One message — one HTTP request: to WhatsApp, Telegram or a bot. One contract instead of an integration per channel: conversation history, inbound messages, mailings, files — and statuses arrive as webhooks.
One message — one request: your own text and attachment for every recipient, and the outcome arrives as a webhook
WhatsApp and Telegram accounts connect by QR code or phone number, Telegram bots by token; the methods are the same
The invite is created by a request: your client connects the account themselves, by link and without access to your account, and the channel id is returned to you
Dialogues and messages are stored on our side: the history is returned by a plain request, with no round trip to the messenger
Not just the fact that someone replied, but the text: an inbound message arrives as an event, and you answer it with the same send method
Sending, delivery and read statuses — for every message and for every recipient of a mailing
Notifications about events — account connection, inbound messages, mailing progress, recipient statuses — with no API polling
When there are many recipients: create, edit a draft, start, stop and cancel — the queue and retries are on the service
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 spreads the sending out and pauses the mailing if the messenger restricts the account
The service checks whether a number is registered in the messenger: those that are not receive no message and come back with a separate status
Prompt help with integration and troubleshooting
There is no password: sign in with Yandex, Google or email.
In your account, open the API section and click Create key. The token is shown once — save it right away.
WhatsApp or Telegram accounts — by QR code or phone number, Telegram bots — by token. The request is the same.
One request and the message goes to a particular person. When there are many recipients, the same API creates a mailing: messages, recipients, start.
Statuses for every message and every recipient of a mailing, replies and inbound messages — by request or webhook.
The messenger API is useful wherever messages to customers should go out automatically — on an event in your system, one at a time or to the whole base at once.
A message goes out when a deal stage or order status changes — the manager does not have to remember whom to notify and when.
Order confirmation, payment, packing and delivery: the customer gets every step in the messenger instead of searching for an email.
A form request gets a reply within a minute, while the lead is hot — in the messenger the person left in the form.
A reminder a day before the visit and confirmation of the appointment with a reply message: fewer empty slots in the schedule.
Tracking number, shipment status changes and a delivery notification — without courier calls or support requests.
Invoices, receipts, subscription renewals and technical notifications go out from your system on its own schedule.
Promotions and special offers by base segments: the segment is built on your side, the sending and the pace are handled by the service.
Interview invitations and application statuses by recruiting stage — the candidate replies where it is convenient for them.
A survey after a purchase or visit, and the answers come back to your system as an event — together with the message text.
The same request works for messenger accounts and for bots: adding one more channel is a different value in the request, not a new integration. An account is needed to write to someone you have not messaged before; a bot is for working with your own subscribers, and it needs no phone number at all. A mailing is the same channel, just with many recipients.
If you would rather not develop anything, the same capabilities are available without code: the CRM integration is a ready-made link with Bitrix24 and amoCRM, where the conversation runs in the customer card and segments and funnel events come from your CRM, and connecting an AI assistant via MCP lets you describe customer communication scenarios in plain words.
From your regular accounts registered in the messenger app. An account is connected by QR code or phone number — via the API or in your WSENDER account — and stays connected for subsequent sends. Recipient replies arrive to the same accounts. If a mailing goes from a bot, the bot itself is the sender, and no phone number is needed at all.
You create the key yourself in your WSENDER account: the API section → 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.
The rate is set by the plan: 60 requests per minute on Basic, 300 on Light and 1,200 on Professional. The limit is counted per project, not per key: issuing new keys does not extend it.
A request above the limit is rejected with code 429 and a Retry-After header: repeat it after the specified time. This is enough for a regular integration — funnel events, order confirmations, statuses; do bulk sending as a mailing, not as a stream of single requests.
