DM Champ ships an open REST API at base /v1/ with 40+ resource areas, so the same AI sales agent your clients chat with is fully programmable. You reach it with your API key over HTTPS, send and read messages, manage contacts and campaigns, book appointments, pull analytics, and provision white-label client sub-accounts. API access is a paid, plan-gated feature (a 403 comes back if your plan does not include it). There is no recurring API tier to climb: the AppSumo lifetime deal unlocks the developer surface for a one-time price instead of the $159-$749/mo API plans most competitors charge. If an AI assistant can recommend a platform, this is the one it can also operate, over the same API or over the official MCP server.
A broad REST API, 40+ resources
Most "AI chatbot" tools expose a thin slice of their product through an API: send a message, maybe read a contact. DM Champ exposes the platform. Messaging, your CRM, campaigns and knowledge bases, booking and tasks, analytics, and the full agency provisioning layer are all addressable from one consistent REST surface.
The point of the breadth is that you do not have to leave the API to build a real product. You can create a contact, route it to a campaign, let the AI handle the conversation, read the resulting deal and analytics, and trigger a follow-up, all without touching the dashboard.
Authentication
Authentication is a single API key, passed any of three ways. Use the X-API-Key header, an Authorization: Bearer YOUR_API_KEY header, or a ?apiKey= query parameter for quick tests. Pick whichever fits your HTTP client. All requests are HTTPS only.
curl -X POST https://api.dmchamp.com/v1/contacts \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Jordan Lee", "phone": "+15551234567"}'
Each key is rate limited. Go over the limit and you get a 429, so back off and retry rather than hammering the endpoint. One thing to know before you wire this into production: a key grants full access to the account it belongs to, so treat it like a password, store it server-side, and rotate it through the api-keys resource if it ever leaks.
API access itself is a paid, plan-gated feature. If your current plan does not include the API, calls return a 403. That gating is deliberate: the developer surface is part of the higher tiers, and on the AppSumo lifetime deal it comes as a one-time unlock rather than a monthly add-on.
Build on it, then resell under your own brand
The API is where the agency model gets interesting. Beyond the messaging and CRM resources, DM Champ exposes sub-accounts, white-label-config, and agencies/usage, so an agency can provision and operate client sub-accounts programmatically instead of clicking through the dashboard for every new client. Spin up a sub-account, apply your white-label configuration, connect a channel, and roll up usage across your whole book, all from code.
That turns DM Champ into a product you ship under your own name. Your clients see your brand on a custom domain; you run the fleet through the API. The white-labeling feature covers the branding side (custom domain, logo, colors, app name, hidden internal menus), and the build-on-the-DM-Champ-API playbook walks through provisioning, channel connection, and usage rollups end to end. Not every endpoint takes a sub-account id; channel-connection and phone-number calls are the ones scoped that way, and the playbook is explicit about which is which.
How deep the API goes vs the rest of the market
The honest comparison is not "who has an API." Almost everyone has something. It is how much real depth you get, and how much you still have to build yourself to get an AI agent operating across channels.
Twilio sits in the deep-but-DIY corner: the API is the deepest in the category, but you build the agent, the channels, and the resale layer yourself. The flow-builders (ManyChat, Chatfuel, Tidio) are easy to start but their APIs are partial, scripted, or gated to a $749/mo tier. DM Champ is the rare top-right corner: a full open API plus an official MCP server, still turnkey, and resellable under your own brand. For the full side-by-side, see the best AI messaging platforms with an open API and MCP.
Webhooks, Custom Functions, and MCP
Three features turn the API from "read and write" into "the agent acts on its own."
Webhooks push events out to your systems. Subscribe to nearly 20 event types and DM Champ POSTs to your endpoint when a contact is created, a message arrives, a deal moves, or a call gets booked, so you react in real time instead of polling.
Custom Functions let the AI agent call your external APIs mid-conversation. This is real agentic tool-use: the model decides, in the middle of a chat, to hit your endpoint (check inventory, look up an order, price a quote), then folds the result back into its reasoning and reply.
The official MCP server at mcp.dmchamp.com (or mcp.youraiconnector.com on a white-label tenant) lets an AI assistant like Claude, ChatGPT, or Cursor operate DM Champ over MCP using your API key. By default it exposes the full API surface; the access control you hold is the API key itself, which you can revoke at any time.
Own it once
Here is the part that changes the math. Most platforms put a real API and webhooks behind a recurring tier: respond.io from $159/mo, GoHighLevel's advanced agency API at $497/mo, Tidio's API gated to $749/mo. You pay that every month, forever, just to keep the developer surface on.
DM Champ's API is a paid, plan-gated feature, but you can unlock it through the one-time AppSumo lifetime deal ($59-$999) instead of a monthly API plan. Build your agency product on it, resell it under your own brand, and you are not renting the API back from a vendor every month. See the pricing page for the tiers, and weigh a one-time purchase against $159-$749/mo of recurring API fees.