Refresh
Exchanges a refresh token (sent as the Bearer credential) for a freshly rotated access + refresh pair. Self-service for the token holder — no secret key required. The previous refresh token is honored for one rotation as a grace window; replaying an older one revokes the customer’s tokens.
How it works
The just-replaced refresh token is honored for one more rotation (a grace window so a dropped response or a second app instance doesn’t lock the customer out). Replaying a refresh token that is more than one generation old is treated as theft and revokes the customer’s tokens.Response
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Body
No body. The refresh token is supplied as the Bearer credential; the response is a freshly rotated access + refresh pair.
Response
OK
Access token (1h, or non-expiring if indefinite), prefixed am_jwt_.
Access-token expiry, ms since epoch. null for indefinite tokens.
Rotating refresh token (24h). Omitted for indefinite tokens.
Refresh-token expiry, ms since epoch. Omitted for indefinite tokens.