Read and write the third-party credentials stored in your workspace, so you can find the id of the credential a data connector should authenticate with, and store a new one without leaving your integration. Reading requires an OAuth token with the read_auth_tokens scope; creating and updating require the write_auth_tokens scope and an access token associated with a teammate. You can create a text credential to send yourself, or an oauth credential whose access token Intercom obtains and refreshes automatically via the client-credentials grant. Only credentials with a token_type of text can be updated. No endpoint ever returns a credential value, client secret, refresh configuration, or OAuth configuration.
Returns a paginated list of the workspace's stored third-party credentials. Use this to discover the id of a credential you want a data connector to authenticate with — that id is not otherwise available over REST. Only metadata is returned; credential values are never exposed. The list is not exhaustive: credentials a teammate created are listed, as are those created by some Intercom integrations, but credentials installed by an app package, those created by most other integrations, and those minted for an individual teammate's MCP access are not.
Intercom API version.
If you omit the header, the API uses the version set in your app package, and 1.0 if none is set.
- 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
curl -i -X GET \
'https://api.intercom.io/auth_tokens?per_page=20&starting_after=string' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Intercom-Version: 2.18'successful
An array of auth token objects.
{ "type": "list", "data": [ { … } ], "pages": { "type": "pages", "per_page": 20, "next": { … } } }