API integration
Everything you do in the dashboard is available over REST: build an audience, update a script, launch a campaign, pull the statistics and the conversations. The key is issued in the dashboard and permissions are ticked per section — your CRM, n8n or backend gets exactly what you allowed.
API access is included with the account rental — there is nothing extra to pay for it.
Not a separate, cut-down interface but the same platform sections you see in the dashboard. API integration is for cases where campaigns have to be created from your system and the result has to come back into it.
Create a list, import contacts, queue a chat-parsing task, read the collected people and their variable values. The task status while collection runs comes from here too.
Read a dialogue script and its steps, create a new one or edit an existing one. Useful when the texts live on your side and have to reach the platform automatically.
Create a campaign, tie it to an audience, a script and accounts, start and stop it. Plus daily statistics, run history and a per-contact report.
Lists of threads and the contents of a specific conversation with its status and conversions — so leads and their context end up in your CRM, not only in the dashboard.
The state of your rented accounts: what is ready, what is being prepared, what is under a restriction. Handy when volume is planned on your side.
Balance and operation history. Needed if you track spending from your own system or resell volume to clients.
A key has no “everything allowed by default” mode. Permissions are granted per section and separately for reading and writing — an integration gets exactly the slice it needs.
You can issue as many keys as you like: one for the CRM, one for an n8n scenario, one for a contractor. Any of them is revoked in the dashboard and access disappears at once — the other integrations keep working.
The four setups people most often come to the API for.
The moment the right conversion appears in a conversation, your backend pulls the thread and the contact and opens a deal — no manual transfer, no “we forgot to export”.
A new client list lands in your database — a campaign launches. The platform is the executor here; the decision belongs to your process.
Texts and branches live on your side and reach the platform automatically. An edit is made once — in your repository.
Daily statistics and run history go into BI, where Telegram sits alongside ads and email — and is measured by the same rules.
Pick by who makes the calls: a person, an AI agent or your code.
All three share the same permissions: what the key forbids, neither the agent nor a script will do.
No separate developer sign-up is needed — the key is issued in the same dashboard.
The API section of the dashboard. One key per integration — that way revoking it later costs you nothing.
Only the sections this integration needs, and read-only if it has no business writing.
The key travels in the Authorization header as an ordinary Bearer token. No request signing, no certificate exchange.
From a CRM, from n8n, from your own backend — anywhere an HTTP request can be sent.
The API drives the platform. The Telegram actions themselves, and working in plain words, live in the neighbouring sections.
Issue a key in the dashboard and make your first call. API access comes with the account rental — from $90 a month.
Userbot API
MCP server
Metrics and analytics