Developer Overview
Build on the ChatGenius messaging layer: receive every customer message as a webhook the moment it arrives, send replies from your own system, and read or manage your data over REST. Supports Facebook, Instagram, SMS, WhatsApp, and Telegram.
Add-on · $29/month · Requires Creator+ planOverview
The Webhook & API Add-on gives you programmatic access to the ChatGenius messaging layer. Three surfaces, one API key:
Every inbound message, comment, lead, appointment, and escalation forwarded to up to 3 HTTPS endpoints in real time, signed and retried. 14 event types.
Send replies (free-form text or approved WhatsApp templates), react to DM messages, and show typing indicators on all five channels, from your server.
Read and manage contacts, conversations, messages, tags, appointments, and your team over 19 endpoints. Includes POST /v1/messages, the recommended send for new integrations.
Use them independently or together. The common pattern: receive events via webhook (see the Event Reference for all 14 types), process them in your own system, and reply through the Send API or POST /v1/messages.
For teams that want to disable ChatGenius AI entirely and handle all replies themselves, see Global External Reply Mode.
Getting Started
Requirements
- An active ChatGenius subscription on the Creator, Professional, or Business plan
- The Webhook & Send API add-on purchased from your portal (Add to plan →)
- A publicly accessible HTTPS endpoint to receive events (for webhook forwarding)
Five-minute setup
- Log in to your ChatGenius portal and open Integrations → Webhook & Send API
- Create an endpoint: your HTTPS URL, the event types it should receive, and its data-sharing declaration. New endpoints start disabled
- Copy the endpoint's signing secret and wire up signature verification
- Send a test event from the portal and confirm your handler verifies and acknowledges it
- Enable the endpoint. Real events start flowing
- Create a named API key and make your first call: GET /api/v1/account returns your plan and endpoint config
You can run up to 3 endpoints and up to 10 named API keys, each rotatable independently. Endpoint secrets rotate with a 24-hour grace window; API key rotation is immediate. Details: Receiving Webhooks and Authentication & API Keys.
Sending Messages
There are two ways to send, driven by the same engine with the same request body. They differ only in URL and response shape.
Recommended for new integrations. Part of the REST API: v1 envelope, UTC ISO-8601 timestamps, stable machine-readable error codes.
The original endpoint (/api/meta/webhook-send.php), fully supported. If your integration already uses it, nothing changes.
Both cover every action (send_message, react, unreact, typing_on), every channel, WhatsApp templates, idempotency, and cold outbound on SMS, WhatsApp, and Telegram.
Channels
The event envelope, signing, and Send API work identically on every channel. Each channel also has details unique to it — its inbound sub-block, routing identifier, supported actions, and limits. Those live on dedicated pages:
DMs, reel and post shares, and comments. Reactions, typing, and the 24-hour / 7-day messaging window.
Twilio SMS. Encoding & segments, STOP/START opt-out, and the SMS error reference.
WhatsApp Cloud API. Free-form text within the 24h window, plus approved templates.
Telegram Bot API. chat_id routing, no messaging window, send_message and typing_on.