Verify a magic-link token → open a session
GET
/v1/auth/verify
const url = 'https://beta-api.plune.ai/v1/auth/verify?token=example';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://beta-api.plune.ai/v1/auth/verify?token=example'Where the link in the sign-in email lands. The dashboard calls it (api.ts → verify) with the token from the URL, receives the session cookie, and every later read goes with that cookie. A token is single-use and short-lived, so a second click on the same link answers 401. The browser’s step alone — nothing for a CLI or a collection to call; a CLI gets its credential from POST /v1/tokens.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ” token
required
string
Responses
Section titled “ Responses ”Signed httpOnly plune_session cookie is set
Media type application/json
object
ok
required
boolean
userId
required
string format: uuid
Example generated
{ "ok": true, "userId": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"}Missing token
Expired / already-used / forged token