Developer API & MCP

What you can build with it

The REST API exposes the same objects you manage in the dashboard, so anything you set up by hand can be scripted. The chatbot endpoints let you list every bot in a workspace, create a new one, fetch a single bot by its ID, and delete it. A separate group controls presentation: updating a bot's appearance, and uploading or removing the icons it shows in the chat window. The messaging endpoints let you send a message into a conversation and update one that has already been sent.

That set covers most of what teams actually want automation for. Provisioning a bot per customer when you run a multi-tenant product. Keeping branding in sync when a client changes their colours. Pushing a message into a live conversation from a system that is not Conferbot — an order-status update from your ERP, a shipping notification from your fulfilment tool. Webhooks handle the other direction: your endpoint receives events as they happen instead of you polling for them.

Alongside the REST API, Conferbot ships an MCP (Model Context Protocol) server that exposes the same operations as tools an AI assistant can call directly. If you would rather ask an assistant to spin up a bot than write the HTTP call yourself, that is the path. Either way, the API integration feature page covers where this sits in the product.

Authentication

Every request carries a bearer token in the Authorization header — Authorization: Bearer <token>. Tokens are issued from your Conferbot account, and the interactive request builder in the documentation sends the same header, so you can paste a token in and confirm a call returns what you expect before writing a line of code. Treat the token like a password: keep it in a server-side environment variable, never in front-end JavaScript, and rotate it if it is ever exposed.

API, Zapier, or a native integration?

Reach for the API last, not first. If the system you want to connect already has a native connector, use that — the full list lives under integrations — because native connectors handle token refresh, retries and field mapping that you would otherwise own forever.

If there is no native connector but both sides are on Zapier, the Zapier integration usually gets you there in an afternoon with nothing to deploy and nothing to keep running. The REST API earns its keep when you need something neither can do: per-tenant provisioning at volume, logic that has to execute inside your own backend, or a flow whose latency budget a scheduled Zap cannot meet.

Debugging your integration

Most integration failures are not bugs in your code — they are the messaging platform underneath saying no. When a call fails, start with the status code and the platform error. The error code reference decodes what WhatsApp, Telegram, Messenger and the rest return, with the cause and the fix for each code. If calls only fail sometimes, check the platform limits reference: rate caps, messaging windows and template quotas produce failures that look random until you know the number you are hitting.

For webhooks specifically, the webhook debugging guide works the causes in order — unreachable endpoint, wrong subscription, signature mismatch, a handler too slow to acknowledge. And before you ship a payload, the free tools include checkers for things that are easy to get subtly wrong, like a Telegram bot token or a WhatsApp message template.