You link an existing WhatsApp number to FlareSend with a QR code or a pairing code, the same way you link WhatsApp Web. Your application then calls our REST API, and messages go out from that number. FlareSend is not Meta's WhatsApp Business Platform and is not affiliated with Meta.
Updated 12 November 2026
instance_id in the message body.POST https://api.flaresend.com/send-message with recipients, type, and text. Point a webhook at your HTTPS URL to receive replies.API traffic uses HTTPS. We keep usage metrics for the dashboard: message counts, delivery status, and timestamps. We do not keep the content of your messages for product analytics. The WhatsApp session credentials that keep the link alive are stored encrypted. If the session drops because of a network blip, we reconnect with that saved session. If the number is logged out on the phone, you link it again.
Only message people who expect it. That means a code they just requested, a receipt for a payment they made, or an order update they agreed to at checkout. Ask in plain language, store the answer, and honour STOP.
There is no green tick on this path, and WhatsApp's own rules still apply. The comparison with Meta's Cloud API is the place to decide which one you actually need.
On the phone, open WhatsApp, then Linked devices, then Link a device. Scan the QR code FlareSend shows, or enter the pairing code. That creates a linked session for that number, the same mechanism WhatsApp Web uses. Your server then sends through that session with the instance API key.
Say what you will send, on which number, and how they can stop. A checkout checkbox such as "Send my receipt and delivery updates on WhatsApp" is enough for transactional messages. Store the answer. Do not add them to promotions unless they agreed to that separately.
Use the official WhatsApp Business Platform when you need a verified business name, approved templates, or more than about 10,000 messages a day, especially to large marketing lists. FlareSend is the faster path for opt-in transactional messages from a small team. See the comparison page for the full trade-off.