Yes, Intercom has a REST API, documented on its developer platform. You create an app in the Developer Hub, then use an Access Token for your own workspace's data or OAuth for public apps that reach other people's data. A first call can be a POST to api.intercom.io/contacts to create a contact.
Everything starts with an app
Intercom's developer platform documents a REST API and an API reference, along with guides for the Messenger, Inbox, Contacts, Tickets, Help Center and Reporting. Its rule is that everything is an app. To use the API at all, you create an app in the Developer Hub, and that app is pre-installed to the workspace you select.
The quickest path is short. In the Developer Hub, click New App, name it, pick the workspace and click Create app. Copy the Access Token from the app's Authentication page, then send a request with an Authorization: Bearer header. The docs' example creates a contact with a POST to api.intercom.io/contacts. You can also send an Intercom-Version header to pin the API version, and the docs show the versions in a picker.
Access Token or OAuth: the choice that matters
| Access Token | OAuth | |
|---|---|---|
| Use it for | Your own workspace's data | Public apps reaching other people's Intercom data |
| Typical jobs | Private apps, scripts, automation | Apps other businesses install |
| Whose access | The teammate who installed the app or last regenerated the token | Each workspace that authorises the app |
An Access Token carries the access of the teammate it was issued to. Its conversation access is limited by what that teammate can see. If your script can't find certain conversations, check whose token you're using before you debug anything else.
Because the token is tied to a person, it's worth a note in your offboarding checklist. When the teammate who installed an app or last regenerated its token moves on, check which scripts depend on that token and regenerate it under someone who's staying. It's a two-minute job that saves a confusing outage later.
Never hand your token to a vendor
Intercom is blunt about this. Never give your Access Token to a third party. Asking users for tokens instead of using OAuth is against Intercom's terms and may get API access revoked. So if a tool asks you to paste your Intercom token into its settings, that's a red flag. A legitimate public app connects through OAuth.
A development workspace isn't a copy of your live one
Public app developers must create a development workspace. Private app developers can build on their own Intercom workspace instead. The Intercom Developer Docs list what a development workspace can't do:
- It can't be converted into a production workspace.
- It's only available in the US region.
- It holds a maximum of 20 users or leads, with older extras archived automatically.
- There's no outbound emailing or push notifications.
- Help Center sites can never be set live.
Those limits mean you can't fully rehearse a live email campaign in a development workspace. Plan your testing around them, and keep the US-only rule in mind if your production workspace is hosted elsewhere.
Rate limits
I couldn't read Intercom's rate limit page, so I won't quote numbers here. Check the current numbers in the developer docs before you build anything that sends a lot of requests.
How Help Scout and Zendesk set their limits
Help Scout's Inbox API lists 200, 400 and 800 calls per minute depending on plan. Zendesk lists Support API requests per minute of 200, 400, 400, 700 and 2500 across its five plan levels. If you're comparing help desks rather than APIs, my lists of Intercom alternatives and Help Scout alternatives are a good place to start.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My verdict for a small support team
Intercom's API is well documented and easy to start with. For your own automations, a private app with an Access Token is all you need, as long as the token belongs to someone with the right access. Only build a public app with OAuth if other businesses will install it. If you're unsure which you need, ask one question: will this ever run on a workspace that isn't yours? If the answer's no, keep it private and simple. And never let a vendor talk you into sharing your token.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Is the Intercom API REST?
Yes. The docs describe a REST API with an API reference.
How do I authenticate?
Use an Access Token for your own workspace, or OAuth for public apps.
Is there a test workspace for developers?
A development workspace exists but has limits: 20 users or leads, US only and no outbound email.
Is there a webhook feature?
The developer docs list Webhooks among the guides.
Can I share my token with an app vendor?
No. Intercom says apps must use OAuth rather than asking for Access Tokens.
