Frequently asked questions

A WhatsApp gateway. You link your own WhatsApp number to the platform once, and from then on your software can send and receive messages on that number through a simple HTTP API — for notifications, OTP codes, order updates, support, or a chatbot you build yourself.

No. You connect the number you already use by scanning a QR code from the dashboard, the same way WhatsApp Web works. Nothing is ported and nothing is re-registered.

Register, create an instance, scan the QR code and copy your API key. Sending your first message is a single HTTP request after that — most customers are live in well under an hour.

Either works. Connect whichever account is already on the number you want to automate.

Not continuously. The session lives on our servers. You do need to open WhatsApp on the phone every couple of weeks, otherwise WhatsApp expires the link and you will be asked to scan again.

Yes. Disconnect the instance from the dashboard and scan again with a different number. Your API key and message history stay with the instance.

Yes, if your plan allows more than one instance. Each number gets its own instance and its own key, and outgoing traffic can be balanced across them.

When several numbers are connected, the gateway spreads outgoing messages between them instead of pushing everything through one. Five connected numbers sending 5,000 messages send about 1,000 each, which materially lowers the chance any single number is flagged.

We strongly advise against it, and the platform is not tuned for it. WhatsApp bans numbers that generate spam reports, and that is your number, not ours. Message people who are expecting to hear from you — order updates, reminders, OTP codes, replies — and stay under the daily cap on your plan.

Yes, and it is deliberate. Each instance has a daily cap, 250 messages by default, plus a minimum interval between sends. Both exist to keep your number healthy. Higher caps are available on larger plans once there is a sending history to justify them.

Images (jpg, png, gif, webp), documents (pdf, docx, xlsx, csv, pptx, zip and more), voice notes and video, up to 3 MB per file, supplied either as a public URL or uploaded directly with the request.

It sets the order messages leave the queue, from 0 for urgent traffic like OTP codes up to 300 for the least urgent. Values of 40 and above also add a matching delay in seconds, which is how you pace a large batch without hammering your number.

Yes. A key is tied to a connected number, not to a site, so you can use the same key from your website, your ERP and your mobile app at the same time.

Yes. Point a webhook at your endpoint and you receive inbound messages, delivery receipts and connection events as signed JSON, with automatic retries if your server is briefly unavailable.

The gateway reconnects on its own for ordinary network problems. If WhatsApp invalidates the link from the phone side, the instance moves to a logged-out state, the dashboard shows a fresh QR code, and your webhook is notified so your systems can react.

No, and we would rather say so plainly. This gateway drives a normal WhatsApp session, the same protocol WhatsApp Web uses. That is what makes it possible to keep your existing number with no Meta approval and no per-message conversation fees. The trade-off is that it is not sanctioned by WhatsApp, so use it for conversations your customers expect. If you need the official Cloud API, talk to us and we will set that up instead.