Webhooks let DM Champ push events to your own systems the moment they happen. You subscribe an endpoint URL to the events you care about, and DM Champ sends a real-time outbound POST to that URL whenever one of those events fires. A new inbound message arrives, a contact is created, an appointment gets booked: your server hears about it instantly, no polling, no scheduled jobs, no batch exports. There are nearly 20 event types to subscribe to, covering messages, contacts, appointments, deals, tasks, and more.
This is the "push" half of a two-way integration. Webhooks tell your stack what just happened inside DM Champ. The open REST API lets your stack act on it. Together they turn DM Champ into a programmable component of whatever you are building, not a closed inbox you have to log into.
API access (and the webhooks resource with it) is a paid, plan-gated feature. The cost story below is the interesting part: most platforms charge $159 to $749 every month just to unlock a real API plus webhooks. DM Champ ships the same developer surface through a one-time AppSumo lifetime deal.
Subscribe to events
You register an endpoint URL and pick which events should hit it. From then on, DM Champ POSTs a JSON payload to that URL each time a matching event occurs. The event catalog spans nearly 20 types across the parts of the platform you would actually want to react to:
- New inbound message (a contact replied on any channel)
- New outbound message sent
- Message status changed (delivered, read, failed)
- New contact created
- Contact updated (fields, tags, list membership)
- Appointment booked
- Appointment rescheduled or canceled
- New deal created
- Deal stage changed
- Task created or completed
- Chat session opened or closed
- Bot handed a conversation off to a human
- Campaign events
- Channel connection state changed
A payload tells your endpoint what happened and gives you the IDs to go fetch more detail through the REST API. A new-message event, for example, looks roughly like this:
{
"event": "message.received",
"timestamp": "2026-06-23T14:02:11Z",
"data": {
"messageId": "msg_8f3a91c2",
"contactId": "cnt_7b21d0e4",
"channel": "whatsapp",
"direction": "inbound",
"text": "Do you have any slots tomorrow?"
}
}
Your endpoint receives that, decides what to do, and (if it wants to act) calls back into the API. Subscribe to as many or as few event types as you need per endpoint.
Webhooks plus the API equal a two-way integration
Webhooks and the API are two directions of the same pipe. Webhooks push events out of DM Champ in real time. The REST API lets you read and write back: create contacts, send messages, move deals, book appointments, pull analytics, provision sub-accounts.
That pairing is what makes real automations possible. A webhook fires when a contact replies, your code reads the conversation through the API, scores or routes the lead, then writes the result back (a tag, a deal stage, a follow-up message) through the API again. The webhook is the trigger; the API is the action. Neither alone is an integration. Both together are.
If you want the AI agent itself to call your systems mid-conversation instead of reacting after the fact, that is a separate capability: Custom Functions let the model decide to hit your endpoint and fold the result back into its own reasoning while it is still talking to the customer.
What a real API and webhooks cost elsewhere
Webhooks are not usually a free checkbox. On most platforms they are gated behind a mid or top tier, and the monthly bill to unlock a genuine API plus webhooks runs from $29 all the way to $749. Here is the lowest tier at each vendor that gets you both:
An honest note on that $0/mo: DM Champ's API and webhooks are a paid, plan-gated feature, not a free one. The difference is that the developer surface is unlocked through a one-time AppSumo lifetime deal rather than a recurring monthly API tier, so there is no monthly API fee stacking up on top of your platform cost. You own it once instead of renting it every month. Sources for the tiers above: respond.io, Tidio, Wati, GoHighLevel and ManyChat official pricing, June 2026.
Use it with GoHighLevel, Zapier, or your CRM
A webhook URL is the most universal integration primitive there is, which means DM Champ events drop straight into the tools you already run. Point a webhook at a Zapier (or Make) catch hook and you can fan events out to hundreds of apps without writing code: see the best AI tools for Zapier integration. Point it at GoHighLevel's inbound workflow webhooks to sync contacts and conversations into your agency CRM: see the best AI tools for GoHighLevel integration.
For anything custom, the payload is plain JSON over HTTPS, so any backend, function, or CRM that can receive a POST can consume it. Read the webhooks docs for the event list and payload shapes, then wire it into whatever you already run.