Skip to main content
Call this endpoint once per session to obtain the JWT token required in the Token header of every subsequent Atlas API request. No prior authentication is needed — your credentials travel in request headers.

​
Endpoint

POST /v3/verification/authtoken

​
Request headers

​
Client-Id
string
required
Your client identifier issued by Atlas during onboarding.
​
Client-Secret
string
required
Your client secret paired with the Client-Id, issued by Atlas during onboarding.

​
Response

​
access_token
string
A signed JWT token. Pass this value in the Token header of all protected endpoints.
​
expires_in
integer
Token lifetime in seconds. Atlas tokens expire after 3600 seconds (1 hour).

​
Example

curl --request POST \
  --url https://api.helloatlas.in/v3/verification/authtoken \
  --header "Client-Id: your-client-id" \
  --header "Client-Secret: your-client-secret"

​
Error responses

StatusMeaning
400Missing Client-Id or Client-Secret — one or both headers were not included in the request.
401Invalid Client-Id or Client-Secret — the credentials do not match any active Atlas account.
Store the access_token securely (for example, in memory rather than in local storage) and refresh it before it expires. You can use the POST /refresh-token endpoint to obtain a new token without re-sending your full credentials.