Your numbers, isolated
Keep each WhatsApp number in its own session, with independent credentials and connection state.
Loading your next connection…
A DIRECT CONNECTION TO YOUR CUSTOMERS
Build a WhatsApp REST API integration around your existing number. Connect it by QR code, send messages from your backend, and receive signed webhook events.
EVERY CONNECTION, UNDER CONTROL
Build notifications, customer conversations, and automated workflows with the tools your application already uses.
Keep each WhatsApp number in its own session, with independent credentials and connection state.
Send text, images, video, audio, documents, contact cards, locations, replies, reactions, and polls.
Receive incoming messages and session events through signed webhooks, with retries and delivery history.
Issue scoped account tokens or keys tied to a single session. Revoke credentials whenever you need.
Inspect session events, message activity, connection state, and payment history from your workspace.
Send immediately, then use your application’s jobs for scheduling, pacing, and retries.
EXPLORE THE EXISTING API GUIDES
Learn how to send WhatsApp messages through a REST API, manage QR-linked sessions and verify webhooks. Start with the existing documentation, then follow source-tested Node.js and Laravel tutorials.
Authenticate with a session-bound key and send your first message from your backend.
Read the documentationLink an existing WhatsApp account, inspect QR pairing, and manage isolated session states.
Read the documentationRead payload examples and understand transport acceptance versus recipient delivery.
Read the documentationReceive session and message events and validate the callback HMAC signature.
Read the documentationUnderstand immediate dispatch and implement scheduling, pacing and send retries in your own app.
Read the documentationRelayWA connects through WhatsApp Web-based sessions, not Meta's official WhatsApp Cloud API. Sending and account availability remain subject to WhatsApp platform conditions.
YOUR NEXT INTEGRATION STARTS HERE
Bring WhatsApp into your application with a straightforward HTTP request.
Scan the QR from WhatsApp’s Linked devices.
Keep credentials scoped to a single number.
Use your language. Receive replies through webhooks.
const response = await fetch( "https://relaywa.com/api/send-message", { method: "POST", headers: { Authorization: "Bearer YOUR_SESSION_KEY", "Content-Type": "application/json" }, body: JSON.stringify({ to: "12025550123", text: "Your order is on its way." }) });if (!response.ok) throw new Error('HTTP ' + response.status);const result = await response.json();YOUR STACK, YOUR CHOICE
A standard HTTP API works across languages. Keep your application architecture and add WhatsApp where it belongs.
Use fetch in your Node.js service, then route incoming events to your application.
Explore HTTP integrationConnect with requests or your preferred HTTP client. Build background jobs and event handlers.
Explore HTTP integrationUse Laravel’s HTTP client and queues to send notifications from your existing application.
Explore HTTP integrationConfigure a standard HTTP Request node. This is a manual recipe, not an official packaged RelayWA node.
Explore HTTP integrationHTTP integration examples · published RelayWa SDK packages are not required.
HOW IT WORKS
From your WhatsApp number to your first API message. A straightforward setup that fits your application.
Create a session and scan the QR code from WhatsApp’s Linked devices.
Your session key is created automatically after connection. Copy it to your application server.
Send messages through the API and receive customer replies through signed webhooks.
MAKE IT PART OF YOUR PRODUCT
Your application decides what happens. RelayWa provides the messaging connection.
Connect your order workflow to confirmations, dispatch updates and collection messages.
Send timely reminders and bring confirmations back into your scheduling system.
Route incoming conversations to your support platform and respond from your own tools.
Connect webhook events to your assistant, with your own review and escalation rules.
Keep messaging activity alongside your existing contacts and customer records.
Use message and session events to build the reporting your team needs.
THE DETAILS THAT KEEP YOU IN CONTROL
Independent connection state and session credentials let you keep each number’s integration separate. Account tokens manage only the scopes you choose.
Understand the APIInspect and operate individual numbers without sharing their credentials.
Use session keys for messaging and account tokens for management. Revoke access when needed.
Verify webhook signatures, handle retries and connect events to your own workflows.
A SIMPLE PLAN FOR EVERY STAGE
Compare WhatsApp API costs across RelayWA's monthly and annual subscription plans for QR-linked sessions. The plan cards show current prices and connected-number allowances; your application controls scheduling, pacing and send retries. WhatsApp platform conditions still apply.
Try one number for 7 days. No payment card needed. Explore QR session setup or read how sending works before choosing a plan.
GOOD QUESTIONS, STRAIGHT ANSWERS
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.
YOUR NEXT CONNECTION STARTS HERE
Connect a number and make your first request today.
Start your free trial