Backstage power for developers. Front stage for ops.
Azeer is the local Twilio alternative: a programmable API for WhatsApp, voice and more, plus the operations dashboard your business team runs every day. You open the switches; they run the show.
curl -X POST https://api.azeer.com/v1/messages \ -H "Authorization: Bearer $AZEER_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "channel": "whatsapp", "to": "+9665XXXXXXXX", "template": "order_confirmation", "variables": { "order_id": "A-1043" } }'Illustrative, full reference on request
Programmable, like the big CPaaS
A clean REST API, scoped API keys and real-time webhooks for WhatsApp, calls and every channel, the primitives you expect from Twilio.
Local and compliant
Built for local operating requirements: PDPL-aligned, in-Kingdom data residency, CST-licensed calling infrastructure, and Arabic-native customer communication.
Operations dashboard included
The piece raw CPaaS leaves out: a full operations dashboard, inbox, rules, broadcasts and analytics, so your business team runs day-to-day without you.
Watch it work, live
One request flows through Azeer to the channel, then comes back to you as a real-time webhook.
- Incoming Message200
- Outgoing Message200
- Chat Assigned200
- Chat Closed200
Zero to first message in minutes
Create an API key
Generate a scoped key from Settings → Webhooks & API.
Make your first call
Send a WhatsApp message with a single POST request.
Subscribe to webhooks
Register a URL, pick events and a delivery policy.
A clean REST API
Scoped keys you create and revoke yourself.
- POST
/v1/messagesSend a message on any channel - GET
/v1/conversationsList and filter conversations - POST
/v1/contactsCreate or update a contact - GET
/v1/templatesList approved templates - POST
/v1/webhooksRegister a webhook endpoint
Illustrative endpoints, full reference on request.
Real-time webhooks for every event
Listen for events the moment they happen, so your integrations react automatically.
{ "event": "incoming_message", "data": { "conversation_id": "cnv_8f2a", "channel": "whatsapp", "from": "+9665XXXXXXXX", "message": { "type": "text", "text": "Where is my order?" }, "contact": { "display_name": "Sara", "platform": "whatsapp" } }, "sent_at": "2026-06-16T09:24:11Z"}Delivery policies you choose
From live streaming to self-healing and batching, tune reliability and throughput to your use case.
One request per event, fire and forward.
A continuous, low-latency stream of events as they happen.
Automatic retries with backoff until your endpoint acknowledges.
A representative slice of events, ideal for analytics and load tests.
Events grouped into batches to cut request volume.
Frequent batches for high-throughput pipelines.
The rules engine: when → if → then
No-code automation your ops team builds themselves, fired by triggers, filtered by conditions, carried out by actions.
- Incoming Message
- Outgoing Message
- Text in Message
- Message Type
- Message DateTime
- Message Time
- Customer Channel ID
- Customer Platform
- Customer Display Name
- Add Tag
- Assign & route
- Trigger a webhook
- and more
Backstage is yours. Front stage is theirs.
- ▹REST API for messaging, calls and contacts
- ▹Scoped API keys you create and rotate
- ▹Real-time webhooks across 10+ events
- ▹Six delivery policies for streaming, batching, and retries
- ▹Bi-directional sync with your existing systems
- No-code Rules engine: when → if → then
- A unified inbox across every channel
- A live operations dashboard and analytics
- Compliant broadcasts and an Arabic-native AI Agent
- Runs on the go, no engineering on call