POST /refresh-token — Refresh Access Token

Use this endpoint to silently renew your Atlas session. Pass your current token in the Token header and receive a fresh JWT without needing to re-supply your Client-Id and Client-Secret.

This endpoint belongs to the chat-based onboarding service and uses the /v1 path prefix. If you are using the document verification service exclusively, generate tokens directly via POST /authtoken.

Endpoint

POST /verification/refresh-token

Request headers

string

required

Your current valid token. This can be either an access token or a refresh token issued by a previous call to /authtoken or /refresh-token.

Response

string

A new signed JWT token. Use this value in the Token header of all subsequent protected requests.

integer

Lifetime of the new token in seconds.

Example

curl --request POST \
  --url https://api.helloatlas.in/v1/verification/refresh-token \
  --header "Token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires_in": 3600
}

Error responses

Status	Meaning
`400`	Token header is missing or the request is malformed.
`401`	`Invalid token` — the token is expired, revoked, or does not match any active session.

Authentication

IDP Extraction

Document Verification

Chat Based Onboarding

Bulk Service

Address Match

POST /refresh-token — Refresh Access Token

Endpoint

Request headers

Response

Example

Error responses

​Endpoint

​Request headers

​Response

​Example

​Error responses

Endpoint

Request headers

Response

Example

Error responses