Trade the phone app's sign-in code for its session

POST/api/auth/veyra/mobile/token
No API key
Veyra Docs TeamUpdated Version 1 · History

Trade the phone app's sign-in code for its session.

Returns the person's Veyra Connect session as a vcs_ Bearer token. The app sends it as Authorization: Bearer <token> on API calls and live-event sockets; it works until it is signed out (POST /api/auth/sign-out with the same header) or revoked in Veyra Connect's Connected apps, which ends the phone's access within 30 seconds. Errors carry a code: SIGN_IN_CODE_INVALID, SIGN_IN_CODE_EXPIRED, SIGN_IN_CODE_USED or CODE_VERIFIER_MISMATCH (400, sign in again) and SIGN_IN_FAILED (502, Veyra Connect unreachable).

Authorization

No API key is needed: the token or id in the path, or the request's own signature, authenticates the call. How keys work.

Request body

application/json · required

codestringRequired
code_verifierstringRequired

Responses

200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
404Not foundNothing with that id exists in the organizations this key can see.
502Internal server error

Errors return {"error": "..."}, often with a code and details. See errors and limits.

Profile