Developers
Programmable channels for Azmarq CPaaS
Integrate WhatsApp, SMS, email, voice, RCS, and OTP flows — plus webhooks for delivery and inbound events. Marketing product pages explain the console; these pages explain how to build.
Full request/response docs live at developers.azmarq.com. Generate API keys in your Azmarq console after login.
Channel APIs
Send and operate WhatsApp, SMS, email, voice, and RCS from your stack with account credentials.
Verification
OTP and auth-style traffic on Messaging and transactional email — with voice where entitled.
Webhooks
Receive delivery receipts, inbound messages, and status events without polling.
API directory
Programmable channels + events
Each page covers capabilities and quick start on the marketing site — then jump to live API docs for payloads and auth details.
Open developers.azmarq.com →API
WhatsApp API
Business API conversations, templates, and inbound
Open overview →
API
SMS API
Programmatic SMS via Messaging portal keys
Open overview →
API
Email API
Transactional mail & deliverability controls
Open overview →
API
Voice API
Outbound, IVR handoffs, notifications
Open overview →
API
RCS API
Rich messaging where RCS is enabled
Open overview →
API
OTP API
Verification on SMS, email, and voice
Open overview →
API
Webhooks
Delivery, inbound, and status events
Open overview →
How to start
Console credentials → integrate → webhooks
- 01
Create or log into Azmarq
Enable the channels you need on your plan — WhatsApp, Messaging, Email, Voice, RCS.
- 02
Issue API keys per environment
Prefer separate keys for staging and production; never ship secrets to browsers.
- 03
Send a test on one channel
Start with SMS or Email, then add WhatsApp templates once WABA is ready.
- 04
Subscribe to webhooks
Handle DLR and inbound events idempotently before you scale.
Enterprise / wholesale?
High-volume SMS with binds, routing policy, and CDR often belongs on the SMPP enterprise track— not only REST Messaging. Channel APIs still cover brand and mid-market app traffic.
الأسئلة الشائعة
Developer FAQs
How API pages relate to product modules, credentials, and SMPP.
تحدث مع المبيعاتDeveloper pages focus on integrating channel APIs and webhooks. Product pages explain the full console experience (CTWA, Inbox, Journeys, etc.) for operators and buyers.
Log into the Azmarq console and create credentials for the channels enabled on your account. Samples on the website are illustrative — confirm live base URLs in-console.
Marketing pages show illustrative request shapes. Live paths, fields, and versioning are in the API hub at https://developers.azmarq.com — generate keys in your Azmarq console.
When volume, binds (TX/RX/TRX), routing policy, and CDR-led reconciliation are the product — use the Enterprise SMS (SMPP) track. Brand and app traffic usually starts on Messaging SMS API.
Ready to integrate?
Open the console for keys, or book a walkthrough if you need WhatsApp, Voice, or SMPP packaging clarified first.
