The official WhatsApp API is Meta's WhatsApp Business Platform (Cloud API), used directly or through a partner (BSP). An unofficial API connects to WhatsApp through the WhatsApp Web protocol, as one more linked device, using libraries such as Baileys or whatsmeow.
Differences in practice
| official API | unofficial API | |
|---|---|---|
| number | a number registered on Meta's platform | the number already on your phone |
| cost | charged per template message, by category and country | no per-message cost; only the server |
| starting a chat | approved template only, outside the 24-hour window | free (and that is where the risk lives) |
| groups you already have | not what the platform is built for | read and answered normally |
| risk | low, within the rules | ban if abused |
How to choose
The official API fits a business sending notifications at scale (orders, billing, login codes) that needs a contract and stability. An unofficial one fits people answering those who already talk to them, on their own number, client groups included. WACrew sits in the second camp and its README warns that it is not the official API and that bulk messaging can get the number banned.
Common mistake
Using an unofficial API for cold outreach at volume. It is the main ban trigger. On the official side, the usual mistake is forgetting that only approved templates go out after the 24-hour window.
Questions
Is an unofficial API illegal? Using one breaks WhatsApp's terms of service, and the account can be restricted. That alone is not a crime.
Can I use both? Yes, on different numbers: an official one for notifications and your own for conversations.
In Portuguese: API oficial vs não oficial.



