What it is for
Developers lets your own systems work with your workspace: an ERP, a CRM, your reporting, or an automation tool such as Make or n8n.
- With the API, a system reads your workspace and changes it: it adds contacts and tags, reads conversations, prepares a campaign, and more. It uses an API key that you make here.
- With webhooks, your workspace tells a system the moment something happens: a customer’s message arrives, a contact opts out, a campaign finishes. You give the address to tell, and choose what it hears.
You do not need to build anything to use xconversions. Developers is for a business that has somebody to build the connection, or a tool that offers one.
Where it is
Open Integrations, then Open on the Developers card, or go straight to it. The round button beside the title goes back to Integrations.
A menu down the side has four tabs, and a link:
| On the screen | What it does |
|---|---|
| API keys | The keys your systems call the API with. See API keys. |
| Webhooks | The addresses your workspace tells when something happens. See Webhooks. |
| IP allowlist | Which internet addresses may call the API. See IP allowlist. |
| MCP | The AI apps connected to your workspace, and what they and your keys ask an admin to approve. See MCP overview. |
| Developer guide | How to call the API, keep a system in step, and check that a webhook is really from us. In English, as the API is. |
The developer guide also links to the API’s description as an OpenAPI file, API description (OpenAPI), which tools read to know every call.
Who can set it up, and on which plan
- Developers is an org admin’s. Anybody else who opens it is told that the admins set it up.
- API & webhooks come with some plans. Without them, a key cannot be made and the screen says Not on your plan. The MCP tab depends on its own plan feature.
- Every key made, renamed or deleted, and every endpoint made or changed, is written in the activity log.
What waits for an admin
A system can prepare things, but nothing that reaches your customers or goes live happens without a person. Launching a campaign, publishing an agent, changing what a live agent knows and switching a workflow on are only ever asked for: each call files a request, and nothing happens until an admin approves it on the MCP tab. A request waits 24 hours.
See Approve what an app asks for: requests from a key are approved there in the same way.
Questions
Is the API charged?
Calling the API is part of a plan that includes it. What it makes happen is charged as usual: a reply your agent sends uses AI credits, a message sent goes on Meta’s bill.
Can a system send WhatsApp messages through the API?
A system can prepare a campaign and ask for it to be launched. An admin approves it before anything is sent.
Who do I give the developer guide to?
To whoever builds the connection for you. It opens in the app, from Developer guide on the Developers menu.