Quickstart: Send Your First SMS
This walkthrough gets you from a dashboard key to a real SMS in one request. After it succeeds, use the same apikey header for WhatsApp, RCS, and OTP.
Before you send
Complete this in the portal. Skip any row that does not apply to a test SMS on your account.
| Need | Where | Why |
|---|---|---|
| Wallet credits | Header Wallet / Account | Sends are billed from credits |
| Approved Sender ID | SMS → Utility → Manage Sender ID | Shown on the phone. India: PE ID |
| Approved template (India) | SMS → Utility → Manage Template | DLT template ID. What DLT is |
Gateway type | Assigned to the account | HTTP field type is that gateway API code (for example TRANSACTIONAL) |
| API key | System → Developer → API Key | Next step |
International / non-India routes still need an approved sender and credits; they do not use DLT.
Get an API key
- Log in and open System → Developer → API Key (or Profile → API Key).
- Generate a key and copy it. Do not put it in a mobile app or a public ticket.
- Optional: restrict it with an IP allowlist.
How the header works, rotate, and allowlist: Authentication. Portal screens: Account → API keys.
Note your Base URL
The HTTP API host is https://api.azmarq.com. Open the SMS page to copy the full URL, such as https://api.azmarq.com/v1/sms. In the examples below, $API_BASE_URL is https://api.azmarq.com.
Send one SMS
This is the same body as Send SMS on the Message App page. Replace the sender ID, destination, and type (your assigned gateway API code) with values from your account.
curl --location --request POST 'https://api.azmarq.com/v1/sms' \
--header 'Content-Type: application/json' \
--header 'apikey: YOUR_API_KEY' \
--data-raw '{
"sender": "senderName",
"to": "91XXXXXXXXXX",
"text": "Hello World!",
"type": "TRANSACTIONAL"
}'A successful send looks like this. Store messageId if you will match delivery reports later.
Response
{
"id": "58d63c02-XXXX-XXXX-XXXX-XXXXbb39453",
"data": [
{
"recipient": "91XXXXXXXXXX",
"messageId": "58d63c02-XXXXX-XXXXX-XXXXX-XXXX9bb39453:1"
}
],
"totalCount": 1,
"message": "Message Sent Successfully!",
"error": null
}
type is the gateway API code assigned to the account — for example TRANSACTIONAL. It must match the route on the account. See SMS (Message App).
Prefer POST + JSON. The same fields also work as GET query parameters on /v1/sms.
After a successful send
error is null and HTTP is 200: the API accepted the job. The phone may still show later as PENDING, DELIVERED, or FAILED.
- Save
data[0].messageIdnext to your own user or order id. - Watch SMS → Number report, or configure a DLR URL. Webhooks.
- Do not send the same OTP or alert again until you know this job failed.
If the send fails
| You see | Start here |
|---|---|
Api Key not found | Authentication |
| Sender / template pending | Approve them, or finish DLT for India |
| Insufficient credits | Wallet |
| HTTP 400 | Errors — fix the body, then retry |
HTTP 200, empty data | Number may be on the blocklist |
Full table: Errors → Typical first-send issues.
What to do next
Same apikey and $API_BASE_URL for every channel.
- Recipes — copy-paste SMS, WhatsApp template, OTP, RCS, and DLR matching
- Webhooks — delivery receipts and inbound replies
- SMS (Message App) — DLT, portal campaigns, customize, reports
- WhatsApp App — templates, session window, Commerce, Flows, CTWA
- RCS — bots, cards,
/v1/rcs - Generate and Verify OTP — generate, then validate
Omni SDK — azmarqomni in Node, Python, Go, PHP, Java, C#, and Ruby
Omni MCP — azmarqomni-mcp for Claude Desktop, Cursor, or HTTP hosts
Team Inbox · Automations · Fallback · Account · My CDP