Skip to main content
ChatBridge’s public REST API (/api/v1/) lets you integrate contacts, conversations, messages, templates, tickets, and WhatsApp Flows into your own systems — or hand it to an AI agent as a tool-calling surface. It’s the same API ChatBridge’s own dashboard is built on top of, exposed as a versioned, scoped, rate-limited public contract.

Quickstart

Create an API key and make your first call in under 5 minutes.

Authentication

How API keys, scopes, and the Bearer token header work.

API Reference

Every endpoint, request/response shape, and example.

Rate Limits

60 requests/minute per key, independent of your plan.

What you can do today

  • Contacts — list, create, update, delete, bulk import.
  • Conversations — list, read message history, update status/priority/tags/assignment.
  • Messages — send text, media, interactive, and template messages.
  • Templates — list your approved/pending WhatsApp message templates.
  • Team — list members and team inboxes.
  • Catalogue — read your connected Meta product catalogue.
  • Tickets — full CRUD, comments, activity log, escalation, and pipeline/stage management — the same shared-inbox ticketing system the dashboard uses.
  • WhatsApp Flows — read-only for now: list, detail, metrics, and submission data.

Versioning

/api/v1/ is the only version today. Non-breaking changes (new fields, new endpoints, new scopes) ship straight into v1 without a version bump. A /api/v2/ deprecation policy will be published here before any breaking change ships.

Where this API is going

ChatBridge is building an LLM-agnostic WhatsApp agent runtime — bring your own AI model, plug it into this API (or, soon, an MCP server built directly on top of it), and let it read and act on your WhatsApp inbox with full CRM context. Everything documented here is designed for exactly that use case, not just for human developers writing one-off integrations.