WhatsappQR

The official WhatsApp Business API is a long road: business verification, number provisioning, review cycles. Many owners don't want to wait. WhatsappQR takes the other route — QR pairing — and makes it production-grade.

The flow is the same pattern people know from WhatsApp Web. The user opens the connection page, scans a QR code from their phone, and their personal WhatsApp is now reachable through the platform. Multiple owners can be connected in parallel, each with their own isolated session.

Every inbound message is forwarded to a webhook URL the owner configures. That webhook can point at an AI agent, a CRM, or a plain custom script — the platform does not assume what the owner wants to do with the message. It only moves bytes.

Outbound messages go through a signed API: text, images, other media. Every call is signed so the receiving system can verify the message genuinely came from the platform. That is important when the channel sits on top of a personal account.

The pairing page shows QR refresh state, session health, and a pause button for when the owner wants to silence inbound traffic temporarily without tearing the session down. A "disconnect" action fully ends the session when needed.

Session state is persisted on disk and survives restarts. That means the owner doesn't have to rescan the QR every day — only when something real changes. Rate limits on outbound are enforced to keep the personal account from getting flagged by WhatsApp.

Subscription is checked before every new session so freeloading doesn't happen. The UI is fully multilingual with RTL support where needed. WhatsappQR is deliberately transport-only: no built-in AI, no assumed logic. That makes it composable with whatever the owner runs on the webhook end.