Receive real-time events, trigger agents programmatically and push data anywhere. The Webhooks API is how developers extend MyChatBot to their own stack.
Subscribe to message, lead, deal and hand-off events as they happen.
Fire an agent action from your backend, outbound messages, follow-ups, updates.
Expose your own functions to agents via Webhooks and MCP for bespoke workflows.
Permission-scoped tokens, signed payloads and graceful degradation by design.
The Webhooks API is a do-it-yourself channel in MyChatBot. If your platform can send and receive HTTP requests, your AI agent can talk to its users: your platform posts each user message in, and the agent’s reply comes back to a URL you control.
Built-in channels such as WhatsApp, Telegram or the Website Widget connect directly in the app. The Webhooks API covers the rest: the systems MyChatBot does not support natively.
It is a good fit for:
Inside your own product, users talk to the assistant you connect to this channel, with its instructions, knowledge and connected tools. Your developers own the transport, and MyChatBot runs the conversation.
Every integration rests on three values: an API token you generate, a Unique page_id you choose, and a Reply webhook URL, an HTTPS endpoint on your side. With those in place, each message goes through five steps:
Keep client_id stable for each end user: that is how the conversation continues instead of starting over. You can also send the optional client_name and client_avatar fields, plus an attachments array with file or image URLs.
Include an audio URL in the incoming message and MyChatBot transcribes it automatically, so the agent treats it as a normal message. Turn on Voice reply settings and pick a voice, and replies include an audio URL alongside the text.
The inbound webhook returns standard HTTP codes: 200 when the message is accepted, 400 for a malformed request or a missing required field, 401 when the API token does not match, and 500 when processing failed and the request should be retried.
A Webhooks API conversation is answered by the assistant you configure on the Agent configuration page, so its instructions, Knowledge Base and connected integrations apply here too. Saved changes take effect from the next reply, on every channel.
The Webhooks API is one of the channels on the Channels page, next to WhatsApp, Instagram, Telegram, Viber, TikTok, Facebook, Gmail, SMS, Calls and the Website Widget. A channel connects to one assistant at a time, and you can split channels between several assistants.
MyChatBot also offers other ways to wire in your own systems:
Handoff rules live in Handoff Control on the Agent configuration page and apply to the assistant’s chats:
Read more about human handoff.
A few limits are worth planning for:
No replies coming through? The most common cause is a page_id mismatch or the channel being switched off. A 401 response means the token in your request does not match the API token on the channel screen. To disconnect later, open the same screen and click Revoke.
Before going live, test the assistant in a private chat, and turn the channel switch on only after reviewing the settings. Plans are listed on the pricing page.
Yes, some development work is needed. Connecting the channel in the app takes only a few fields, but your platform has to POST user messages as JSON to MyChatBot and handle the replies at your own Reply webhook URL. If you only need chat on your website, the built-in Website Widget is the simpler option.
Four fields are required: client_id, page_id, platform and text. Optional fields are client_name, client_avatar, audio for a voice message and attachments for file or image URLs. Keep client_id stable so each user’s conversation continues.
MyChatBot posts each reply to your Reply webhook URL as a form-encoded request with text, images, file and audio fields. A long reply may arrive as several parts sent one after another, so append them in order.
Yes, in both directions. Send an audio URL and MyChatBot transcribes it before the agent replies. Turn on Voice reply settings and choose a voice, and replies include an audio URL next to the text.
The most common cause is a page_id mismatch or the channel being switched off. Check that the page_id you send exactly matches the Unique page_id and that Connect agent to this channel is on. A 400 response means a malformed request or a missing required field, and a 401 means the API token does not match.
Yes, with Trigger Outreach in Automations. Your system POSTs a phone number or email, with optional name and context, to a trigger’s unique webhook URL, and MyChatBot creates the lead and can have the agent send a message. The URL itself is the credential, so treat it like a password.
Yes. Handoff Control on the Agent configuration page switches a chat to operator mode by a stop word or by any operator message, and Silent handoff can hide the switch from the client. With Auto return on, the agent is re-enabled automatically after 24 hours or a custom interval.
Grab your API key, subscribe to events and ship your first integration in an afternoon.
Start free