Connect WACRM to your systems and your AI tools
The WACRM API lets your own systems and AI tools work with your WhatsApp CRM: a REST API for contacts, conversations and messages, signed webhooks for every new message, and an MCP server for AI assistants. Every key is scoped and reaches one project only.
By the WACRM team Updated
REST API and webhooks included from the Advanced plan up
MCP for AI tools on the Pro and Enterprise plans
Keys carry only the scopes you grant and reach one project
Signed webhook deliveries with automatic retries
What does the WACRM API do for your business?
Your WhatsApp conversations already live in WACRM. The API lets the rest of your business use them: a store backend sends an order confirmation, a booking system adds a new customer as a contact, a reporting tool reads conversation history, and an AI assistant catches up on a customer before your team replies. Your developers work from the developer reference; AI tools connect through the MCP server.
$ curl https://api.wacrm.ai/v1/contacts \
-H "Authorization: Bearer $WACRM_API_KEY"
{ "data": [ { "id": "…", "name": "Ana",
"phone": "+15551234567", "labels": [ … ] } ] }Catch me up on Ana's chat and send her the order confirmation.
→ read_conversation · contacts:read
→ send_template · messages:send
Ana asked about delivery on Friday. I sent the approved order confirmation template.
How it works
Create a scoped API key
In your Workspace, mint a key and tick only the scopes your integration needs, such as reading contacts or sending messages.
Call the REST API
Your system reads and writes contacts, conversations, templates and messages with the key as a Bearer token. A sandbox base URL lets you test first.
Subscribe to webhooks
Add your own HTTPS endpoint and pick the events you want, such as an inbound message or a delivery status. Each delivery is signed.
Connect your AI tool
For Claude Desktop, Cursor or another MCP client, create a key with the MCP preset and paste the ready-made config into the client.
What do you get with the WACRM API?
A REST API for your WhatsApp CRM
Contacts, conversations, approved templates and messages over HTTPS and JSON, described in an OpenAPI 3.1 file you can download.
Webhooks your system can trust
Every delivery carries an X-WACRM-Signature HMAC-SHA256 header; a failed delivery is retried up to 3 times and can be redelivered from the log.
Five MCP tools for AI assistants
Send a template, read a conversation, add a contact, follow order updates and check the wallet from your AI client.
Scoped keys, nothing more
Each key carries only the scopes you grant. A call outside them is refused with insufficient_scope instead of acting.
One project per key
A project key only reaches its own project. Asking for another project's data returns not found, never someone else's records.
Retries that never send twice
A message send carries an Idempotency-Key, so a retry with the same key replays the first answer instead of messaging the customer again.
Who is the WACRM API for?
Online shops
Send an order confirmation template from your store backend and get the delivery status back on a webhook.
Agencies
Run client projects from one integration: an account key covers several projects, a project key stays inside one.
Teams with an AI assistant
Let Claude Desktop or Cursor catch up on a customer's conversation and add new leads as contacts, within the scopes you allow.
Which plans include the API and MCP?
API keys and webhooks are included from the Advanced plan up. MCP actions for AI tools run on the Pro and Enterprise plans. Plan prices below are per month, billed monthly; see pricing for yearly prices and everything else each plan includes.
| Plan | Price | REST API + webhooks | MCP for AI tools |
|---|---|---|---|
| Premium | $29/month | — | — |
| Advanced | $75/month | Included | — |
| Pro | $179/month | Included | Included |
| Enterprise | $299/month | Included | Included |
How do you keep control of every key?
- Scopes per key. You choose the scopes when you create a key; WACRM scopes such as contacts or messages are always opt-in.
- Project isolation. A project key works inside one project only. An account key, for multi-project integrations, resolves which project it is acting on.
- Webhooks stay opt-in. An endpoint receives your message content, so it needs its own webhook scope, and you can rotate its signing secret.
- Limits for AI tools. An MCP key can carry a monthly action cap, shows when it was last used, and can be revoked in one click.
Which tools does MCP give your AI assistant?
The wacrm-mcp server gives an AI client five tools, each one a WACRM API call made with the
key you created for that client: send_template, read_conversation,
create_contact, notify_order and wallet_balance. The model is whichever one
your client runs, so you keep the AI you already use.
Contacts the agent adds land in your contacts CRM, and for AI that
answers customers inside WACRM itself, see AI agents.
Need the integration built for you?
Our engineers connect WACRM to your CRM, ERP or store, and build connections for your AI agents, as part of custom development. Every project is scoped with you first and quoted with clear milestones. Developers who want to start themselves can follow the API and MCP quickstart. Product names such as Claude and Cursor belong to their owners.
Questions about the WACRM API and MCP
Which plans include the WACRM API?
API keys and webhooks are included from the Advanced plan up: Advanced, Pro, Enterprise. MCP actions for AI tools run on the Pro and Enterprise plans.
Do I need a developer to use it?
For the REST API and webhooks, yes, or our team: custom development connects WACRM to your own systems for you. Connecting an AI tool over MCP needs no code — the Workspace gives you the config to paste.
Which AI tools can connect through MCP?
Any client that speaks the Model Context Protocol over stdio. The Workspace writes the config for Claude Desktop and Cursor, and gives a one-line command for other MCP clients.
Can a key reach another project's data?
No. A project key is tied to one project, and a request for a project the key does not own returns not found. Revoke a key at any time and it stops working at once.
Where is the full technical reference?
On the developer reference page, which lists every endpoint, method and scope from the OpenAPI file, and on the MCP page, which lists each tool and the scope it needs.
Talk to an expert
A person from the WACRM team replies.
Ask which plan fits your integration, or let our team build the connection for you.
Replies within one working day, usually sooner on WhatsApp.
Put your WhatsApp CRM to work in your own systems
Get started, mint your first scoped key in the Workspace, or talk to our team about a custom integration.