Chatwoot API
Chatwoot's REST API for open-source, self-hostable customer support with live chat, email, and social media channel management with full data ownership.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Self-hosted deployments control all security posture including TLS configuration. Cloud enforces TLS. Token-based auth with no scope granularity. Open source allows security audits of full codebase.
⚡ Reliability
Best When
An agent needs to automate customer support workflows within a self-hosted or privacy-sensitive environment where full control over data and infrastructure is a requirement.
Avoid When
You need a managed SaaS solution with zero operational overhead, or require enterprise integrations that Chatwoot's ecosystem does not yet cover.
Use Cases
- • Building AI agent integrations that read and respond to support conversations in real time
- • Automating ticket assignment and labeling based on message content analysis
- • Creating and managing contacts and conversations programmatically in a self-hosted environment
- • Integrating with internal tools via API without data leaving your own infrastructure
- • Querying conversation history and agent performance metrics for reporting agents
Not For
- • Teams requiring SaaS reliability guarantees without managing their own infrastructure
- • Organizations needing deep e-commerce platform integrations out of the box (use Gorgias)
- • Enterprise teams requiring vendor-backed SLAs and 24/7 support contracts
Interface
Authentication
User access tokens generated per agent account via profile settings. Account-level API tokens also available for super-admin operations. No OAuth or fine-grained scopes — token inherits the creating user's role permissions.
Pricing
Open source under MIT license — self-hosting is free with no restrictions. Cloud offering provides managed hosting. Enterprise tier adds SLA support, custom features, and priority assistance.
Agent Metadata
Known Gotchas
- ⚠ API endpoints are versioned (v1, v2) and not always consistent — some resources only exist in one version
- ⚠ Account ID is required as a URL path parameter for most endpoints, not a header — easy to omit when building generic clients
- ⚠ Self-hosted deployments may run older versions with different API behavior — always check the deployed version against docs
- ⚠ Webhook event payloads are not the same format as REST API responses for the same resource
- ⚠ Channel types (web, email, API, WhatsApp, etc.) have different capabilities — not all actions are available on all channel types
- ⚠ Creating a conversation via the API channel allows full programmatic control; other channels have restrictions on message creation
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Chatwoot API.
Scores are editorial opinions as of 2026-03-06.