Stores a third-party credential in your workspace so a data connector can authenticate outbound requests with it. Set token_type to text (the default) to send the credential value as a request header yourself, or to oauth to have Intercom exchange OAuth client credentials for an access token and keep it refreshed. The value you supply is stored encrypted and is never returned by any endpoint, including this one.
Preview Intercom API version. Used for closed beta endpoints or other features under managed availability.
A name for the credential, so a teammate can identify it later.
The credential value. Required when token_type is text. Must be omitted when token_type is oauth. Stored encrypted and never returned by any endpoint.
The request header the credential is sent in. Required when token_type is text. Must be omitted when token_type is oauth, where it is fixed to Authorization.
An optional prefix placed before the credential value in the header, for example Bearer. Must be omitted when token_type is oauth, where it is fixed to Bearer.
An optional description of what the credential is used for.
The OAuth client-credentials configuration Intercom uses to obtain and refresh an access token. Required when token_type is oauth. Must be omitted when token_type is text.
- The production API serverhttps://api.intercom.io/auth_tokens
- The european API serverhttps://api.eu.intercom.io/auth_tokens
- The australian API serverhttps://api.au.intercom.io/auth_tokens
- successful
- OAuth credential
curl -i -X POST \
https://api.intercom.io/auth_tokens \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: Preview' \
-d '{
"name": "Fulfilment API key",
"token_value": "sk_live_9f3c2a7b41e8",
"request_header_key": "Authorization",
"token_prefix": "Bearer",
"description": "Used by the order status connector"
}'successful
An optional description of what the credential is used for.
How the credential is presented to the external API, for example as a header value or an HMAC signature.
The request header the credential is sent in.
The prefix placed before the credential value in the header, for example Bearer.
The domain the credential is scoped to, if one was set.
The time the credential was created, as an ISO 8601 timestamp.
- successful
- OAuth credential
{ "type": "auth_token", "id": "12345", "name": "Fulfilment API key", "description": "Used by the order status connector", "token_type": "text", "request_header_key": "Authorization", "token_prefix": "Bearer", "domain": null, "created_at": "2025-11-15T09:30:00Z", "updated_at": "2025-11-15T09:30:00Z" }