Intercom API
Intercom's REST API for managing customer conversations, contacts, companies, and automated messaging workflows. Enables agents to create and reply to support conversations, manage contact and company records, trigger message sequences, and build AI-powered support bots integrated with Intercom's messaging platform.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
OAuth 2.0 with workspace-scoped tokens. Single-workspace access tokens are straightforward for agent auth. Webhook signature verification available. EU and US data residency options satisfy GDPR requirements.
⚡ Reliability
Best When
An agent needs to read, respond to, or route customer conversations in Intercom, or sync contact/company data for customer success workflows.
Avoid When
You are not using Intercom, or need a simple helpdesk without Intercom's in-app messaging and lifecycle capabilities.
Use Cases
- • Creating and replying to customer conversations from automated agent workflows
- • Managing contact and company data for CRM automation
- • Creating and routing support tickets via programmatic rules
- • Triggering automated message sequences based on agent-detected user behavior
- • Building AI-powered customer support bots integrated into the Intercom inbox
Not For
- • Teams not using Intercom (no value without the Intercom platform)
- • Simple email-only support where a full platform is overkill
- • Teams on tight budgets (Intercom is among the most expensive customer support platforms)
- • Real-time high-volume event-driven messaging at scale
Interface
Authentication
Access tokens for single-workspace integrations. OAuth 2.0 for multi-workspace apps with scope-based permissions. Token-based auth is simplest for agents. Tokens are workspace-scoped. API versioning is mandatory via Intercom-Version request header.
Pricing
One of the more expensive customer support platforms. Most businesses need at minimum the Essential plan ($39/seat/mo) for full API access. Startup program provides free access for qualifying companies.
Agent Metadata
Known Gotchas
- ⚠ API versioning is required via Intercom-Version header — must specify correct version or responses will be unexpected
- ⚠ Replying to a conversation requires correct author type (bot vs admin) — bots need specific Intercom app setup to reply as a bot
- ⚠ Conversations vs tickets have different data models — check which is in use for your workspace before writing code
- ⚠ Contact deduplication by email is not automatic — agents can easily create duplicate contacts without checking first
- ⚠ Webhook signatures must be validated using the client secret to prevent spoofed event ingestion
- ⚠ Rate limits are per workspace, not per token — other integrations on the same workspace consume the shared quota
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Intercom API.
Scores are editorial opinions as of 2026-03-06.