WhatsApp REST API quickstart
Authenticate with a session-bound key and send your first message from your backend.
View API documentationRELAYWA HELP CENTER
Find help with QR-linked sessions, subscriptions, message status and webhooks. For request examples and exact API endpoints, use our developer documentation.
Create a session in your workspace. Open WhatsApp on your phone, select Linked devices, and scan the QR code. Once connected, create a session API key and test your first request.
Yes. Each number has its own isolated session and API credentials. Your subscription determines how many numbers you can connect.
Add an HTTPS webhook endpoint to your workspace. RelayWA delivers message and session events to your application, with retries when delivery fails.
Paid plans use subscription pricing based on connected numbers. There is no per-message fee or monthly message cap. Your application controls sending cadence and retries.
Open the session page to inspect its status and logs. RelayWA’s worker handles recoverable connection interruptions. A logged-out account requires a fresh QR scan.
New workspaces receive a 7-day trial with one number and 50 messages per day. You can test linking, API requests, and webhook integration before choosing a paid plan.
No. RelayWA connects existing WhatsApp accounts using QR-linked WhatsApp Web sessions. It is not the official Meta WhatsApp Cloud API or a Meta business solution provider. Review WhatsApp account policies and integration risks before production use.
No. Outbound messages are sent directly to the connected session. Your application should handle schedules, pacing and bounded retries using a stable clientMessageId to avoid accidental duplicate sends.
Each topic opens the existing English documentation. No separate or duplicated feature pages are needed.
Authenticate with a session-bound key and send your first message from your backend.
View API documentationLink an existing WhatsApp account, inspect QR pairing, and manage isolated session states.
View API documentationReceive session and message events and validate the callback HMAC signature.
View API documentationCHOOSE YOUR WHATSAPP API CONNECTION
These are different approaches, not interchangeable products. RelayWA is an independent QR-linked WhatsApp Web session service and is not authorized or certified as Meta's official Cloud API.
Meta hosts the official WhatsApp Business Platform Cloud API. Its Graph API uses business assets, registered phone numbers and platform access tokens rather than pairing a WhatsApp Web session by scanning a QR code. Choose the official platform when an authorized integration is required.
Meta's Cloud API referenceRelayWA links an existing WhatsApp number with a QR code and exposes REST methods, session state and signed webhooks. Session connectivity can change, and WhatsApp warns that linking through unofficial apps or websites can create security and account restriction risks. RelayWA cannot promise immunity from restrictions or guaranteed message delivery.
WhatsApp's linked-device safety guidanceFor the current session-based send and retry contract, see message dispatch documentation. For pricing differences, see the pricing explanation.
RESPONSIBLE MESSAGING
Before sending, obtain appropriate opt-in, record what each recipient agreed to receive, and respect opt-out or block requests. Use secure server-side credentials, protect QR codes and verify signed webhooks before handling events. A successful API response does not confirm that a person read your message.
Read the WhatsApp Business Messaging Policy and the QR and session troubleshooting guide. RelayWA is not affiliated with or endorsed by Meta or WhatsApp.