Sign in and get a token
Authenticate with email and password and receive the token used by every other API. One token covers Claudia, Cloud Chat and the services that follow — the account you see is derived from it, and the same token is valid against production and staging.
A 200 does not always carry a token. Accounts with a temporary password, or with two-step verification turned on, come back with a challenge instead: no token yet, and a session to answer it with at POST /v1/signin/challenge. Branch on the body, not on the status — id_token present means done, challenge present means one more step.
Body
Response
Either a token, or a challenge to answer before one is issued.
- Option 1
- Option 2
Sign-in completed.
Send THIS one as Authorization: Bearer <id_token>. It carries the identity the APIs authorize on — your email and the accounts your credentials cover. The access token does not.
"eyJraWQiOiJhYmMxMjMiLCJhbGciOiJSUzI1NiJ9..."
Issued by Cognito alongside the id token. Not what the Cloud Humans APIs read.
"eyJraWQiOiJkZWY0NTYiLCJhbGciOiJSUzI1NiJ9..."
Lifetime in seconds.
3600
Always Bearer.
"Bearer"