A single REST API for WhatsApp and Telegram accounts and for bots. It carries the whole mailing: audience, safe pace, statuses and recipient replies. The queue and account protection are on the service — your CRM or website sends one request.
The same methods for both: a WhatsApp or Telegram account connects by QR code or phone number, a Telegram bot by its token
Create, edit a draft, start, stop and cancel mailings, messages and recipients — all via HTTP requests
Contact segments, uploading numbers and field values — name, city, order amount — to be substituted into the text
The pace is set by the auto strategy, not by your code: the service lowers the risk of the account being blocked and pauses the mailing itself if the messenger restricts it
The service checks whether a number is registered in the messenger: those that are not receive no message and come back to you with a separate status
Not just the fact that someone replied, but the text of the reply — pull it into your CRM on an event, with no polling
Sending, delivery and read statuses for every recipient of the mailing
Notifications about events — account connection, mailing progress, recipient statuses — with no API polling
Prompt help with integration and troubleshooting
Sign in with your Yandex or Google account.
Open the API section in the mailing cabinet and click Create key. The token is shown once — save it right away.
A WhatsApp or Telegram account — by QR code or phone number, a Telegram bot — by its token. The request is the same.
Create a mailing, add messages and recipients via HTTP requests and start sending.
Receive delivery statuses for every recipient via the API or WebHook.
There is no separate fee for the API — regular service plans apply. The free Basic plan includes 15 messages per day, which is enough for development and testing. For production volumes: Light — 300 messages per day for $15 / month; Professional — 3,000 messages per day for $40 / month. See the pricing page for details.
WhatsApp and Telegram accounts and Telegram bots. The API is unified: connecting, creating mailings and receiving statuses work the same way for all of them — just specify the channel in the request. A bot differs in two things: it connects by a token instead of a QR code or phone number, and it sends to its own subscribers rather than to uploaded numbers, because the Bot API does not allow writing first.
You create the key yourself in the mailing cabinet: the API section, then Create key. The token is shown once and cannot be recovered later — if you lose it, create a new key and delete the old one. A key belongs to the project, and you can create several keys — one per integration, for example.
The token is passed in the header of every request: Authorization: key YOUR_TOKEN. All methods are described in the API documentation, where you can also run a request with your own key straight from the browser.
