Create a sub-client under your ChatPush multi-customer account. The response contains the sub-customer's own API token — it is shown only here, so save it.

Use it when onboarding a new client of a platform built on ChatPush: each sub-customer gets a separate account, its own messengers and its own subscription.

Requires a multi-customer account: a ChatPush client that may create sub-clients through the API.

Register a webhook URL to receive real-time notifications for specific ChatPush events (e.g. whatsapp_log_out, delivery status updates, incoming messages). Use it when the user wants their server, CRM or automation (n8n, Make, Zapier) to receive replies or react to WhatsApp/Telegram events.

Delete a sent message from WhatsApp or Telegram (tdlib). Only works for messages with final 'Delivered' status. Deletion occurs on all recipient devices.

Only messages sent through ChatPush via the tdlib or whatsapp channels can be deleted; SMS cannot. Use it when the user asks to unsend or recall a message.

Delete a webhook by ID. The webhook will stop receiving notifications.

Get full ChatPush account information including token, balance, dispatch routing, sender names, subscription status and Telegram/WhatsApp sessions count. Use it to verify the token works, check whether the subscription is active, or diagnose undelivered messages (e.g. WhatsApp or Telegram not authorized). For just the balance use get_balance.

Get ChatPush account balance, customer ID, available dispatch routing channels, and registered sender names. Use it when the user asks how much money is left, before a large mailing, or to find a valid sender_name for SMS.

Get the current status and full details of a specific message delivery by its ID. Returns status, operator info, phone, scheduled time, costs and more. Use it after send_message or send_file when the user asks whether a message was delivered or read, or why it failed — the status is explained in plain words.

Get a link to the QR-code page that connects a WhatsApp or personal Telegram account to ChatPush. Open the link in a browser and scan the code with the phone that will send messages.

Use it when sending fails because the messenger is not connected (WhatsApp session not started, Telegram not authorized), or when setting the account up for the first time. Check the result afterwards with get_account.

Look up phone number information including country, mobile operator name and brand. Useful before sending to verify the number and determine routing. Also returns the number normalized to international format, e.g. when the user wrote it with spaces or brackets.

Show one sub-client by its customer_id: subscription status and expiry, and whether WhatsApp and Telegram are connected.

Requires a multi-customer account: a ChatPush client that may create sub-clients through the API.

Get list of all UTM tags (utm_marks) configured in the ChatPush account for tracking message dispatches. Use it to reuse an existing label as utm_mark in send_message, send_bulk or send_file, so statistics stay grouped.

Get details of a specific webhook by its ID: the URL it posts to and the event types it subscribes to.

List the sub-clients of your ChatPush multi-customer account with their subscription status and whether WhatsApp and Telegram are connected.

Requires a multi-customer account: a ChatPush client that may create sub-clients through the API.

List all registered webhooks for this ChatPush account. Use it to see where events are delivered or to find a webhook ID before updating or deleting it.

Send the same message to multiple phone numbers at once. Supports scheduling, UTM marks, dispatch routing cascade, Telegram usernames and tdlib user IDs.

Use it for announcements, campaigns or reminders to a list of recipients. For one recipient, or when a delivery ID is needed for tracking, use send_message.

Send a file (document, image, audio, video, contact) to a recipient via WhatsApp or Telegram. File is uploaded as multipart/form-data. Images under 10MB sent natively, larger files as download links active for 7 days.

Use it when the user wants to share a document, photo, voice message, video or contact card. Provide the file as exactly one of: file_path (local file), file_url (downloaded by the server) or file_base64 (with file_name).

Supported: pdf, doc, docx, ppt, pptx, xls, xlsx, zip, 7z; ogg, opus, mp3, aac, amr, 3gp; jpeg, png, webp; mp4; vcf. Max 100 MB. Recipient rules are the same as send_message.

Send a text message via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK (notify), or MAX (max), with optional cascade fallback between channels. Supports scheduling, priority, reply-to, typing simulation, and delivery callbacks.

Use it when the user asks to text, message, notify or reply to one person or group chat. For many phone numbers use send_bulk; for documents, images, audio or video use send_file.

Recipient: phone is required, except for personal Telegram (dispatch_routing ["tdlib"]) where username or tdlib_user_id can be used instead, and WhatsApp where whatsapp_lid can be used.

Returns the delivery ID for get_delivery_status and delete_delivery.

Rename a contact in the ChatPush web messenger, so operators see a person's real name instead of a phone number. The name is stored as the CRM client name of the conversation.

Find the conversation by phone, Telegram username or Telegram user ID — at least one is required. If the contact has both WhatsApp and Telegram conversations, both are renamed.

Update an existing webhook — change its URL or the list of event types it subscribes to. Pass only what should change; types replaces the whole list.