Chatery WhatsApp

fajri-rinaldi-chan‘s WhatsApp API backend: an Express.js 5 server wrapping baileys 7.x, with multi-session account management, Socket.IO event streaming, group administration, media handling, bulk send with background processing, webhooks with event filtering, an OpenAPI-documented REST surface, and Docker Compose deployment. MIT, 214 stars, 73 forks, created 2025-12-15 and last pushed 2026-07-01. Routed here on 2026-08-05.

Why this one matters more than its star count

Every source this spoke held before it came through the front door. This one does not use the Cloud API, has no WABA, submits no message-template, has no BSP above it and pays nothing per message. It authenticates by scanning a QR code from an ordinary WhatsApp account and speaks the WhatsApp Web protocol directly through baileys.

It is the spoke’s first documented instance of the unofficial path, and it arrived as working software with a dashboard and Swagger docs rather than as a description of one.

What it does that the official path makes hard

Multi-session is the clearest tell. One deployment holds many logged-in WhatsApp accounts at once, with sessions persisted so they survive a restart. On the official platform the equivalent means one WABA per business, verified phone numbers, and per-number onboarding. Here it means another QR scan.

Bulk messaging is the second. Queued background sending to many recipients is a first-class feature. On the Cloud API the same intent runs into message-template approval, marketing-category billing under per-message-pricing, and the customer-service-window. None of those exist here.

Labels are exposed for WhatsApp Business accounts, so the project reaches into business features while staying outside the business platform.

What it is not

There is no LLM and no agent loop anywhere in it. That makes it the clean test of the seam the spoke’s synthesis left open: a WhatsApp integration with the model removed is entirely a transport concern, and this one belongs here rather than in ../agentic-tooling-wiki without argument. Compare whatsapp-chatgpt-bot, which is the same shape with the model as the point.

What the source does not say

The README documents capabilities and says nothing about the consequences of using them. Meta’s terms prohibit unofficial clients, and the practical risk of a banned number, the reliability of a reverse-engineered protocol against WhatsApp’s changes, and the legal position of bulk messaging without opt-in are all unaddressed. That silence is normal for the genre and it is the main thing to hold against the page.

Tier

T3 — the maintainer’s own repository, describing itself. The stack and feature list are verifiable from the code and the API surface; nothing about durability, ban rates, or deliverability is evidenced.

baileys · whatsapp-business-platform · wapi-go · fajri-rinaldi-chan · synthesis