One API for Instagram, Messenger, WhatsApp, SMS & Telegram

Five channels through one integration: Instagram DM, Facebook Messenger, WhatsApp Business (via Meta Cloud API), SMS (via Twilio), and Telegram. Same authentication, same idempotency, same HMAC-SHA256 signing secret, and the same response envelope across all five. Inbound events carry a platform identifier, and outbound messages route on conversation_id, platform_user_id, or to_phone.

REST API v1 covers 133 endpoints, every section of the portal. Contacts with upsert, tags and custom fields. Conversations, messages and assignment. Appointments: availability, book, reschedule, cancel. Flows: node catalogue, validate, create, publish, activate, pause, analytics and sessions. Comment triggers with a simulator, and the AI Comment Manager approval queue. Content Studio posts with media, scheduling and publishing. Knowledge base FAQs, services and documents, plus detected knowledge gaps. Team seats and invitations, the AI configuration, blocked users, opt-outs, your webhook endpoints and API keys, and an account endpoint for plan and usage. Cursor pagination and one envelope throughout, and an OpenAPI 3.1 spec at /api/v1/openapi.json. Full reference at /docs/rest-api.

Thirty-one event types in eight groups. Messages: message.received, reel and post shares, postbacks, and the per-channel sms, whatsapp and telegram inbound events. Comments: comment.received, comment.trigger_fired, comment.handled. Leads: email and phone captured. Appointments: booked, cancelled, rescheduled. Conversations: escalated, resolved, assigned. Contacts: tag added or removed, stage changed, updated, field changed. Posts: scheduled, published, failed. Flows: published, activated, paused, session completed. And message.send_failed. Every event carries the same envelope with conversation context, contact metadata including tags, stage and custom fields, and the platform identifier. Payloads at /docs/webhook-events.

Yes to both. Create multiple named API keys and rotate or revoke any one of them independently, so a contractor or a staging integration can be cut off without disturbing production. You can also register up to three webhook endpoints, each with its own signing secret, its own event selection, and its own pause or go-live switch. Delivery is gated per endpoint, so you can bring a new consumer online without touching the one already running.

Every webhook payload is signed with HMAC-SHA256 using that endpoint's signing secret. The signature is sent in the X-SumGenius-Signature header. Your server verifies it by computing HMAC-SHA256 of the raw request body with your secret and comparing the result. Secrets rotate per endpoint without downtime.

Failed deliveries retry with growing delays over about 18 hours: 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours. After the last failure the event lands in a dead-letter queue you can inspect and replay from the dashboard once your endpoint is healthy. Delivery logs show every attempt with its response code and which endpoint it was aimed at. If Inbound Body Purge is enabled, inbound SMS events use exactly one attempt with no retries so the body can be scrubbed inside a tight window.

Yes. Send free-form WhatsApp text inside the 24-hour window, or an approved template any time outside it. Pass template_name, template_language such as en_US, and template_components alongside to_phone. Components are passed to the Meta Cloud API verbatim, so any header of text, image, video or PDF, any body variable, and any button parameter defined in your template editor is honored.

Yes, through the same send endpoint by including to_phone in E.164 format. The sending number is server-controlled to your provisioned Twilio number and cannot be overridden, which is what keeps A2P 10DLC campaigns compliant. Each successful outbound call counts as 1 against your monthly SMS quota regardless of how many segments Twilio splits it into. SMS requires Professional or Business tier and a provisioned number.

External Reply Mode turns off the ChatGenius AI for a single conversation, one channel, or every channel at once. Inbound messages still reach your webhook, but nothing is generated or sent on our side. Your backend replies through the API instead. This is the setting to use when ChatGenius is the messaging layer and your own system owns the conversation logic.

A per-account compliance toggle for SMS. When enabled, inbound message bodies are forwarded to your webhook with one delivery attempt and then immediately scrubbed from our storage: the message row, the webhook event log and the SMS queue. Conversations become metadata-only locally, keeping message id, timestamp, sender number, direction, delivery status and ticket reference. Built for healthcare-adjacent and privacy-strict deployments where your server is the system of record. Requires AI off on SMS, since purge clears the same context the AI would reply from.

The authenticated v1 surface allows 200 requests per minute per client with a 20 per second burst, inside a system-wide ceiling of 1000 per minute. A sliding window is used rather than a fixed one, and every response carries RateLimit headers so you can back off before being throttled. Outbound sending also respects each platform's own limits, and idempotency keys prevent duplicate delivery when you retry.

In the portal, open the Webhook & Send API section. Create a named API key for authenticating requests, then register an endpoint URL and choose which of the 31 events it should receive. Each endpoint gets its own signing secret. Send a test delivery from the panel before going live, and watch it land in the delivery log. Full reference at /docs/rest-api for endpoints, /docs/webhook-events for payloads, and /docs/mcp for the MCP server.

Yes, and from any other assistant that speaks the Model Context Protocol. Two ways. Hosted: paste https://sumgenius.ai/api/mcp into claude.ai, ChatGPT, Cursor or any client with a custom connector, click Connect, and approve it once in ChatGenius. Local: the chatgenius-mcp npm package runs on your computer with an API key. Either way the assistant gets 61 tools: read and reply to conversations, manage contacts and tags, check availability and book, build and publish flows, approve comment replies, schedule posts, and edit the knowledge base. Tools that reach a person or publish are flagged so the client asks you first, you choose read-only or read-and-act when you connect, and you can disconnect any assistant from Settings. Documented at /docs/mcp.