Baileys
A TypeScript/JavaScript library that speaks the WhatsApp Web protocol over a WebSocket, letting a program act as a logged-in WhatsApp client without a browser. Maintained by WhiskeySockets, MIT, 10,598 stars and 3,274 forks, last pushed 2026-08-04. Discovered through chatery-whatsapp, which is a server built on it.
The second door into WhatsApp
This spoke was built on the assumption that reaching WhatsApp programmatically means the whatsapp-business-platform: a WABA, business verification, approved templates, metered delivery, and optionally a BSP. Baileys is the other door, and it skips all of it.
| Cloud API path (wapi-go) | Baileys path (chatery-whatsapp) | |
|---|---|---|
| Account | WABA + verified business number | Any WhatsApp account |
| Auth | Access token issued by Meta | QR-code pairing, as a linked device |
| Business-initiated message | Approved message-template only | Any message |
| Cost | per-message-pricing per delivered template | None |
| Identity gate | Business verification | None |
| Sanctioned by Meta | Yes | No |
What it costs instead
The gates do not disappear so much as change into different risks. Meta's terms prohibit unofficial clients, so the enforcement moves from approval before sending to account bans after. The protocol is reverse-engineered, so it breaks when WhatsApp changes and the library has to catch up. And nothing external constrains volume or consent, which is the property that makes the approach attractive for bulk sending and also the reason it draws bans.
Officially it is unmetered; in practice the price is paid in reliability and account risk rather than per message.
Why the spoke keeps it
It is not a business-messaging platform and it is not sanctioned by one. It sits here because it is the limit case of this spoke's central claim — that the policing is the product (synthesis). A widely used library that reaches the same users while paying none of the tolls is the strongest available evidence about what the tolls actually buy, and for whom.
Re-verified 2026-10-07 (staleness queue)
11.3k stars (+700), 3.4k forks (+126), still active. The material change is a major version: "As of 7.0.0, multiple breaking changes were introduced into the library," with a migration guide at a new site, baileys.wiki, replacing the README as the primary doc — still incomplete. The maintainer now offers paid support and sponsorship.
This sharpens, rather than contradicts, the page's own "what it costs instead" section: the protocol breaking on WhatsApp's side was already named as a risk; a breaking major version of the library itself, mid-migration to a new doc site, is a second, independent source of the same instability — an integrator on the unofficial path now has to track both WhatsApp's changes and Baileys' own.
Related
chatery-whatsapp · whatsapp-business-platform · per-message-pricing · message-template · synthesis