Blog / Guide

Unofficial vs official WhatsApp API: what to choose

The choice between the unofficial and official WhatsApp API is one of the first decisions for anyone wanting to automate WhatsApp for their business. On one side there's the WhatsApp Web via QR code solution, often called "unofficial", with no per-message cost; on the other the official Meta Cloud API, with approved templates and green check. There's no absolutely right choice: it depends on volume, message type and risk tolerance. Let's look at the real differences, no slogans.

What "unofficial" means: WhatsApp Web via QR

The WhatsApp Web via QR code mode connects your WhatsApp number (Business too) using the same technology as WhatsApp Web: you scan a QR and your number becomes operable from a platform. The big advantage is the absence of per-message costs and the speed of activation. The flip side is that Meta offers no official guarantees on this automated use: if you abuse the volume or send unwanted messages, the number can be limited or blocked.

• No per-message cost
• Immediate activation with a QR code
• Uses your existing number
• More fragile: no official guarantee, ban risk if abused

What the official Meta API is (Cloud API)

The official Meta Cloud API is the channel supported and designed by Meta for businesses. It requires template approval for proactive messages, but in exchange it offers stability, the green check of a verified account and anti-ban protections when used correctly. It's built for volume and for serious transactional communications. The cost follows Meta's per-conversation model, billed directly by Meta.

• Stability and official Meta support
• Green check of a verified account
• Approved templates with anti-ban protection
• Per-conversation cost billed by Meta

Direct comparison

When each solution is worth it

WhatsApp Web via QR is ideal for starting out, for modest volumes and for those who want to test automation without per-message costs: support for a few customers, small lists, chat management by a team. The official API becomes the mandatory choice when volume grows, when you need reliable transactional notifications (order confirmations, reminders) and when the green check and reputation matter. Many businesses start with the QR and migrate to the official API when they scale.

If you mainly send transactional notifications (orders, reminders, confirmations) to many contacts, start directly with the official API: the stability and anti-ban protection make the per-conversation model worth it.

The ban risk explained without alarmism

The number block is neither automatic nor inevitable: it depends on behavior. Sending unsolicited messages to purchased lists, spamming in bursts or ignoring unsubscribes increases the risk, especially in QR mode. Respecting consent, sending expected messages and maintaining a good reputation reduces the risk on both tracks. The official API additionally offers a quality system managed by Meta.

How to do it with SendApp

SendApp offers both tracks in the same tool: you connect WhatsApp Web via QR code with no per-message cost to start, or you activate the official Meta API with templates and green check when you scale. In both cases you have the CRM with tags, broadcast campaigns, the trainable AI agent and the multichannel inbox. With the Cloud API messages are billed by Meta with no SendApp markup. Plans start at 19 euros a month and over 30,000 businesses already use SendApp.