API keys
Response
OAuth access tokens
An OAuth client exchanges a signed assertion for an access token atPOST /oauth/token, then sends the token as a Bearer token:
expires_in seconds and works on every endpoint that accepts an API key. An OAuth client acts for your organization’s default team, with the same team rules as a key.
How the API picks a credential
- A request with
Authorization: Beareris authenticated with that token. The API ignoresx-api-keyon that request, even when the token is invalid. - An API key sent as a Bearer token is refused with
401. Send API keys only inx-api-key. - Send one credential per request.
401 message, see 401 Unauthorized.
Endpoints without credentials
Every other endpoint returns
401 without a valid credential.
Revocation and expiry
- A revoked key stops working within five minutes.
- An expired key stops working at its expiry time. Sixtyfour emails your organization before longer-lived keys expire; see Expiration.
- Archiving a team revokes its keys.
- Disabling or deleting an OAuth client invalidates its tokens on their next request.
Request IDs
Every response carries anX-Correlation-ID header:
correlation_id. Log it with each request, and include it when you contact support. It is the Request ID column in exported usage logs.