Connect WhatsApp in minutes
Raseel gives you one API that stays put: start in the Sandbox, move to fast QR onboarding, then upgrade to the official Meta Cloud API without rewriting your application.
The platform is being built. We do not publish metrics or testimonials before they are real.
curl -X POST https://whats.azzamkh.sa/api/v1/messages \
-H "Authorization: Bearer $WA_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"to": "+9665XXXXXXXX",
"type": "text",
"text": { "body": "Your code is 481902" }
}'
# 201 Created
# { "id": "msg_...", "status": "queued", ... }The same request works across Sandbox, QR and Meta. The provider is an internal detail, never part of the API contract.
This call needs an API key from your workspace. Create one under Developers after you sign in — the sample will not work as pasted until you replace the key.
Three paths to production
Test instantly, then link a real number, then move to the official Meta path. Your code does not change at any of those steps.
- Step oneAvailable now
Sandbox — test instantly
A shared test number is assigned to you with a verification code, so you can confirm the integration in minutes with no setup and no review.
- Step twoComing soon
QR — your real number
Link your existing number by scanning a QR code. This path is not officially supported by Meta, so we treat it as replaceable infrastructure and default to conservative safety limits.
- Step threeComing soon
Meta Cloud API — the official path
Move to the official platform: approved templates, published throughput limits and Meta support. The same channel migrates without new keys or new code.
Upgrading from QR to Meta is a migration, not a rewrite
The workspace, the channel's logical identity, contacts, conversations, templates, automations, webhooks and API keys are preserved. What changes is the provider behind the API.
Everything around messaging, in one place
Each item below carries its real status. We do not describe a capability as available before it works.
- Available now
Unified send API
POST /v1/messages with optional Idempotency-Key, plus per-message state and a full transition timeline on read.
- Available now
API keys
Separate test and live keys, shown once at creation, revocable one at a time without disturbing your other integrations.
- Available now
Arabic and English at parity
Interface, documentation and email in Arabic first and English in full, with genuine RTL rather than a mirrored afterthought.
- Coming soon
Shared inbox
One team conversation view with assignment and status, over the same channels your integration uses.
- Coming soon
Campaigns
Batched broadcasts that always rank below authentication and service messages, validated before they launch.
- Coming soon
Automations
Event-triggered flows: auto-reply, assignment, tagging and outbound webhook calls.
- Available now
Templates
One unified template that translates into what each provider expects, including the Meta approval path.
- Coming soon
Teams and roles
Roles and permissions enforced by the server on every request, never by hiding a button in the interface.
- Available now
Webhooks
Signed events for every state change and inbound message, with a delivery log and replay.
Built to be read — by engineers and by coding agents
One stable contract, examples that work when pasted, and documentation that is machine-readable by design.
One API that does not move
The provider is an operational detail. Moving a number from QR to Meta changes neither the API contract nor your application code.
Stable error codes
Every failure carries a stable code and a request_id, so your integration branches on identifiers instead of matching English prose.
Friendly to AI coding agents
An llms.txt is published today, with an OpenAPI document and copy-paste examples in preparation, so an agent can learn the API from the source instead of guessing at it.
Documentation and API reference
Public docs, an OpenAPI document, a Postman collection and generated SDKs are in preparation. The docs page says exactly that today rather than showing a half-written reference.
Open the docs pageLaunch plans
These plans and limits are the platform's own configuration — the same plans seeded into the database. An administrator can change any value, and plans are versioned so an existing customer's limits do not shift underneath them.
Prices will be set in Saudi riyals (SAR) and are not announced yet. They will be published before commercial launch and remain subject to change. We would rather show no number than a number we have not decided.
Free
free
Free
One production channel and a single seat. The plan a new workspace starts on.
- Production channels
- 1
- Team seats
- 1
- Contacts
- 500
- API keys
- 2
- Webhook endpoints
- 1
- Active automations
- 2
- Campaigns
- Not included
- Log retention
- 7 days
- Support
- Docs
Starter
starter
Announced before launch
Small teams: three channels, five seats, campaigns enabled.
- Production channels
- 3
- Team seats
- 5
- Contacts
- 10,000
- API keys
- 10
- Webhook endpoints
- 5
- Active automations
- 20
- Campaigns
- Included
- Log retention
- 30 days
- Support
- Standard
Growth
Most suited to a growing teamgrowth
Announced before launch
Scaling teams: ten channels, twenty seats, priority support.
- Production channels
- 10
- Team seats
- 20
- Contacts
- 100,000
- API keys
- 25
- Webhook endpoints
- 20
- Active automations
- 100
- Campaigns
- Included
- Log retention
- 90 days
- Support
- Priority
Enterprise
enterprise
Negotiated
Negotiated limits. Every quantitative entitlement is open until an override narrows it.
- Production channels
- Open
- Team seats
- Open
- Contacts
- Open
- API keys
- Open
- Webhook endpoints
- Open
- Active automations
- Open
- Campaigns
- Included
- Log retention
- Open
- Support
- SLA
One further plan, sandbox, backs evaluation workspaces and is not customer-selectable, so it is not listed here.
The questions worth asking first
Short answers, including the ones that are not flattering.
Is this the official WhatsApp API?
Partly, and it depends on the path. Meta Cloud API is fully official. The QR path is built on WhatsApp Web and is not officially supported by Meta — we never present it as though it were. Sandbox is for testing only.
Can my number be restricted on the QR path?
Yes, that risk is real. WhatsApp's policies restrict unauthorised clients and unwanted bulk messaging, and no daily limit can guarantee an account's safety. That is why QR channels default to a conservative outbound limit, campaigns rank below service traffic, and we recommend the Meta path for serious production use.
What happens when I move to Meta?
The same channel migrates. Your workspace, contacts, conversations, templates, automations, webhooks and API keys are preserved, and your application code stays as it is. Only the provider behind the API changes.
How is the Sandbox different from production?
A Sandbox session is a shared test number that talks to one verified recipient, meant for confirming an integration. It is not for real customers, and its keys are in test mode and clearly marked in logs.
Is the Arabic support real or a later translation?
Arabic is the platform's default language and right-to-left is part of the design rather than a layer on top. English is at full parity, and you can switch from any page.
Where is my data stored?
Today the platform runs on a single server operated by the platform team, with its database and object storage in the same environment. We have not yet published a contractual data-residency commitment; when we do it will live in the privacy policy, not on a marketing page.
When will prices be announced?
Before commercial launch. The limits on the pricing page are real and already configured in the platform; the money is not published until it is a final decision.
Is the platform ready for production use?
Not yet. Accounts, workspaces, API keys and the messaging core are built; real number connections, the shared inbox and campaigns are still in progress. The features section states the status of each part.
Create an account and read the API
Accounts, workspaces and API keys work today. Create a key, look at the shape of a request, and follow the remaining paths as they ship.