Intercom API

Name: Intercom API API
Brand: Intercom API
Availability: InStock

✓ Official Vendor SpecCRMCustomer Supportbearer133 EndpointsREST

For Agents

Send and reply to Intercom conversations, manage contacts and companies, and read help-centre articles and tickets across an Intercom workspace.

Quickstart

Get started with Intercom API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"reply to an Intercom conversation"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Intercom API API.

Open new conversations from contacts and reply on behalf of admins or users

Search contacts and companies with the workspace's data attributes and custom fields

Create and update tickets, attach contacts, and move them through ticket states

Publish, list, and search help-centre articles, collections, and sections

GET STARTED

Start building with Intercom API API

Explore with Jentic

View OpenAPI Document

The Intercom API exposes the platform's customer messaging, support, and help-centre operations across 133 endpoints, covering conversations, contacts, companies, tickets, articles, segments, tags, and the workspace's data attributes. Authentication is a bearer access token issued via Intercom's OAuth flow or a personal access token from the developer hub. Regional servers are available for EU and AU workspaces in addition to the default US production endpoint, and version 2.13 is signalled through the standard Intercom-Version header workflow.

Use Cases

Patterns agents use Intercom API API for, with concrete tasks.

★ Support Agent Reply Automation

Support teams use the Intercom API to draft, send, and triage replies on conversations from a custom UI or AI assistant rather than the Intercom inbox. POST /conversations/{id}/reply sends the message body as either an admin or a user, while GET /conversations/{id}/parts returns the existing back-and-forth so the agent can write a contextual response. Integration is hours rather than days because of Intercom's stable v2 schema.

Reply to Intercom conversation 9145872 as admin 73821 with the message 'Your refund has been issued and will appear in 3-5 business days.'

Contact and Company Sync

Product and growth teams sync user and account data from their backend into Intercom contacts and companies so messaging and segmentation reflect product reality. POST /contacts and POST /companies create or update records keyed on external_id, and the search endpoint supports filtered queries with operators across attributes. Daily sync jobs replace the older brittle CSV import flow.

Upsert an Intercom contact with email user@acme.com, name 'Avery Chen', and custom attribute 'plan' set to 'pro'

Help Centre Content Management

Documentation teams manage help-centre articles, collections, and sections through the API rather than the Intercom UI, enabling Markdown-source-of-truth workflows or AI-assisted article generation. POST /articles publishes new pieces, GET /help_center/collections lists the navigation structure, and PUT /articles/{id} applies edits. This unblocks doc-as-code workflows for support content.

Create a new Intercom article titled 'How to update your billing address' under collection 8821 and publish it

Agent-Driven Customer Triage

An AI agent sits behind a workspace inbox, reading new conversations through GET /conversations and classifying them by topic, sentiment, and urgency. It then assigns the conversation to the right team via PUT /conversations/{id}/parts with an assignment body, tags it for reporting, and drafts a suggested reply for human approval. Jentic handles the bearer token isolation so the agent never sees the raw access token.

Read all unassigned Intercom conversations from the last hour, classify each as 'billing', 'technical', or 'general', and assign to the matching team

Key Endpoints

133 endpoints — the intercom api exposes the platform's customer messaging, support, and help-centre operations across 133 endpoints, covering conversations, contacts, companies, tickets, articles, segments, tags, and the workspace's data attributes.

METHOD

PATH

DESCRIPTION

POST

/conversations

Create a new conversation

POST

/conversations/{id}/reply

Reply to a conversation as admin or user

POST

/contacts/search

Search contacts with filters

POST

/contacts

Create a contact

POST

/companies

Create or update a company

POST

/tickets

Create a support ticket

POST

/articles

Publish a help-centre article

POST

/tags

Apply or create a tag

POST

/conversations

Create a new conversation

POST

/conversations/{id}/reply

Reply to a conversation as admin or user

POST

/contacts/search

Search contacts with filters

POST

/contacts

Create a contact

POST

/companies

Create or update a company

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Intercom bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive a scoped token at execution time; the long-lived OAuth or PAT never enters the agent's prompt or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'reply to an Intercom conversation') and Jentic returns the matching Intercom operation with its input schema, so the agent doesn't need to read 133 endpoints of documentation.

Time to first call

Direct Intercom integration: 1-3 days to wire OAuth, handle rate-limit retries, and validate against the right regional server. Through Jentic: under 1 hour once the workspace is connected.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zendesk API

Ticket-first support platform versus Intercom's messaging-first model

Choose Zendesk when the workflow is ticket-and-queue centric with strong SLA reporting; choose Intercom for in-app chat, proactive messaging, and product-led support.

Alternative

Freshdesk API

Multi-channel helpdesk versus Intercom's conversation-and-messaging core

Choose Freshdesk for omnichannel ticketing across email, phone, and social with cost sensitivity; choose Intercom for product messaging and help-centre integrated workflows.

Alternative

Drift API

Conversational marketing platform versus Intercom's broader support and engagement scope

Choose Drift when the focus is sales chatbots and pipeline conversion; choose Intercom for blended marketing, support, and help-centre needs.

Complementary

HubSpot Conversations Inbox Messages API

CRM-side record of conversations that pairs with Intercom messaging

Use HubSpot Conversations alongside Intercom when sales context lives in HubSpot and Intercom is the live chat front door — sync conversation summaries between the two.

FAQs

Specific to using Intercom API API through Jentic.

What authentication does the Intercom API use?

Intercom uses bearer token authentication. Pass an OAuth access token or a personal access token in the Authorization header as 'Bearer {token}'. Jentic stores Intercom tokens in the MAXsystem vault so the agent never sees the raw token; only short-lived scoped access reaches the runtime.

Can I reply to a conversation programmatically with the Intercom API?

Yes. POST /conversations/{id}/reply sends a reply with a message_type of 'comment' (visible to user) or 'note' (admin-only). You set type to 'admin' or 'user' to control authorship and supply the admin_id when replying as a teammate.

What are the rate limits for the Intercom API?

Intercom enforces a default 10,000 calls per minute per workspace for most endpoints, with lower per-second concurrency caps. The actual remaining budget is returned in X-RateLimit-Remaining and X-RateLimit-Reset response headers; treat HTTP 429 as the canonical signal and back off.

How do I create a ticket through Jentic?

Search Jentic for 'create an Intercom ticket'. The SDK returns the POST /tickets operation with the ticket_type_id, contact, and ticket_attributes schema. Run pip install jentic, await client.search('create an Intercom ticket'), then await client.execute(...) with the ticket payload.

Does the Intercom API support EU and AU data residency?

Yes. The spec lists three servers: https://api.intercom.io (US), https://api.eu.intercom.io (Europe), and https://api.au.intercom.io (Australia). Choose the server that matches the workspace's hosting region — calls to the wrong region return 401.

Can I publish help-centre articles via the API?

Yes. POST /articles creates an article with a title, body (HTML), state ('published' or 'draft'), and a parent collection or section. Use GET /help_center/collections and GET /help_center/sections to look up the parent IDs the article should sit under.