QR pairing
Connect from the WhatsApp Linked Devices screen without transferring number ownership.
Pair an existing WhatsApp account by QR code, operate it through an API and monitor the session without migrating the number.
An API route for teams that need their current WhatsApp number to remain usable on the phone.Connect from the WhatsApp Linked Devices screen without transferring number ownership.
Track connection state, last heartbeat and re-pairing requirements.
The paired account can continue to be used from its existing WhatsApp client.
A workspace administrator starts pairing in ChatRail and scans a short-lived QR code from WhatsApp. ChatRail stores the resulting provider session securely and exposes a connection identifier to your application. The QR code is temporary and must not be logged, cached publicly or shared across workspaces.
| Linked Devices | Meta Cloud API | |
|---|---|---|
| Existing normal account | Designed for this | Migration or business setup may apply |
| Meta approval | Not part of pairing | Official onboarding applies |
| Connection durability | Session may require re-pairing | Managed official platform |
| Platform status | Unofficial route | Official Meta API |
Treat connected, degraded, disconnected and pairing-required as explicit states. Pause sends when a session is not healthy, alert the workspace owner and resume only after the provider confirms recovery. Do not silently discard queued messages or retry without a bound.
Choose the official Cloud API when formal Meta support, approved templates, regulated procurement requirements or maximum connection durability matter more than using an existing normal account.
No. It works as a linked device, although WhatsApp controls device and session behavior.
Yes. ChatRail monitors state, but applications must account for re-pairing and delayed sends.
No. It should have a short lifetime and be visible only to an authorized workspace user.
Validate the connection, delivery state and reply path before increasing traffic.
Gain Access