Refresh Access Token

GET 
/api/v2/access_token/refresh

Refreshes the Access Token using a valid Refresh Token to extend session validity. The resulting token lifetime depends on the expiresin parameter and the User's registration profile (see the expiresin parameter).

Request

Responses

200

OK: The request was successful.

400

Bad Request: The request could not be understood by the server due to malformed syntax.

401

Status Unauthorized: The request requires User authentication.

403

Status Forbidden: The client does not have permission to access the resource.

429

Too Many Requests: The client has sent too many requests in a given amount of time.

Response Headers

X-RateLimit-Limit
Sustained requests allowed per second for the bucket that rejected this request.
Example: 100
X-RateLimit-Remaining
Tokens left in that bucket.
Example: 0
X-RateLimit-Reset
Unix timestamp, in seconds, at which the next token becomes available. This is the earliest time a retry can succeed.
Example: 1757942400