Message clients on WhatsApp and Telegram right from the chat

The agent calls the third version of the Wazzup24 API with the key of your account. The first thing it reads is the list of channels — that is both a check of the key and a map of what can actually be written through: WhatsApp, Telegram, Instagram. From there contacts, deals and pipelines, message templates, unanswered conversations and the webhooks you set up go into the work, all within one account and the channels connected in it.

A channel in Wazzup is a live link to a real messenger account, and that link breaks: the QR expires, the connection to the phone is lost, the channel goes unpaid. From the outside the account still looks fine, so the agent checks the state of the channels and names the ones that dropped, with the reason, instead of sending messages into a channel that will deliver nothing. You learn about a channel that went down before the client is left without an answer.

On sending, the main restriction comes not from Wazzup but from WhatsApp: the 24-hour conversation window. While the client has written within the last 24 hours a regular message goes out; once the window is closed only an approved WABA template arrives, and the agent picks the right option rather than sending blind. It writes by phone number or username through a specific channel, edits what it sent and syncs contacts.

The API key opens the channels and contacts of the whole account, not of a single manager — it is worth handing out with that in mind. Incoming messages arrive over a webhook: the agent parses a message right after delivery instead of polling the account in circles, and if no webhook is configured it says plainly that it sees the history but not new conversations. It holds the request rate itself, and when data or permissions are missing it says so directly rather than showing an empty list of dialogues.