Live session health
Check the session's current connection. Health is confirmed only while WhatsApp is connected.
GET /sessions/:id/healthConnect a WhatsApp number to your product. Send and receive messages and media, including group messages, and integrate with simple HTTP requests and real-time webhooks.
Pilot access is currently available by request.
Interactive example — no messages are sent
POST /api/v1/whatsapp/<SESSION_ID>/messages/text
Authorization: Bearer <SESSION_TOKEN>
Content-Type: application/json
{
"to": "<RECIPIENT_CHAT_ID>",
"text": "Your order is ready."
}Wathook lets you connect WhatsApp to any CRM, ERP, website, SaaS product or AI agent with simple HTTP requests — including existing group conversations. Use the returned message ID to correlate delivery and read updates from webhooks.
Clean JSON endpoints, one token per session, immediate sends, signed webhooks and a dashboard for your sessions and subscriptions. Pair your number, set a webhook, and start testing.
Every WhatsApp number gets its own scoped token. View and copy your token from the dashboard, then use it on your server.
Send a request and receive its result. No duplicate-prevention key or send queue. Each new request sends once.
Incoming messages, delivery and read updates, groups and channel activity — signed and filterable per target, with one attempt and no replay.
Messaging, media, group reads and webhooks — the toolkit for bots, notifications, support and integrations.
Check the session's current connection. Health is confirmed only while WhatsApp is connected.
GET /sessions/:id/healthRead your groups and their participants, send group messages and receive group changes by webhook.
Several targets per account, event filters, custom headers, HMAC signatures and one attempt per event and target.
POST /hooks/whatsapp → 200 OKText, images, video and documents such as PDFs and spreadsheets.
Receive WhatsApp delivery and read evidence by webhook. A timeout is shown clearly and never blocks your next request.
Read available chats and messages, check whether a number is on WhatsApp, and manage chat labels.
GET /contacts/:id/check-existsWrite the integration yourself, connect the tools you already use, or put WhatsApp inside your product under your name.
Call the REST API from any language and handle webhooks on your server.
Read the API guideAnything that sends HTTP requests and receives webhooks can drive WhatsApp.
See how it worksCreate client sessions with the Manager API and give each client only its own session token.
Partner programPay for each session, for as long as you need it.
Send your requirements and the number of sessions you need for review.
Use your session token and one HTTP request. The response says whether WhatsApp accepted it — results immediately.
Configure your receiver for incoming messages and delivery updates. Each event gets one attempt per target, without replay.
Keep your key on your server. Messages are sent immediately, and the response says whether WhatsApp accepted them. Every request is one new message; a timeout may mean it was sent, so check before sending again.
Keep the WhatsApp message identifier and receive subsequent delivery evidence at your callback endpoint.
A timeout says the message may have been sent. Your next request can proceed; nothing is resent automatically.
One token per session; revoke or reissue anytime.
Every WhatsApp session is billed on its own for 1, 3 or 12 months. The prices below are for one session (one number).
The total for several sessions is shown before you pay. Sending the contact form does not charge you.
No. Wathook is an independent service that connects through WhatsApp's linked-device (WhatsApp Web) protocol. It is not affiliated with or endorsed by Meta or WhatsApp, and it is not the official Cloud API. Account restrictions or protocol changes can affect availability.
No template approval flow is involved. Once your number is paired with a session, you can send and receive through the API. Use it only with people who have agreed to hear from you; WhatsApp can restrict accounts that behave like spam.
Open your session and scan the QR code from WhatsApp → Linked devices on the phone that owns the number, or use a pairing code when available. If WhatsApp asks for passkey linking, Wathook cannot complete it; restart the session to try again.
Yes. The API works as a linked device, so the phone and WhatsApp Web keep working alongside it. WhatsApp may occasionally reset linked devices and ask you to pair again.
Text, images, video and documents (PDF, spreadsheets and other files). You can also read available chats, groups and messages, and receive incoming messages, delivery and read updates and session changes by webhook.
You pay for each WhatsApp session (one number) on its own, for 1, 3 or 12 months, and each session has its own expiry date. There are no per-message fees. The session is created once your payment is confirmed; nothing renews automatically.
No. Each message is sent immediately and the response reports the result from WhatsApp. Sent is not a delivery receipt: delivered and read updates arrive later by webhook. A timeout may still have sent the message. Wathook does not resend it or block your next request.
Yes. Partners buy prepaid session credits in the dashboard. The Manager API creates sessions from those credits and deletes owned sessions. Give each client only its own session token.
Planning a larger number of sessions or need a custom arrangement? Tell us what you need and the Wathook team will follow up by email.
Sending this form does not charge you
Custom quotes for larger numbers of sessions
Already have an account? Sign in