Azmarq — One Platform · Every Conversation

Developers · SMS

Programmatic SMS via Azmarq Messaging

Use API keys from the Messaging portal to send SMS from your applications — with sender IDs, reports, and billing tied to your Azmarq account.

Built for: App backends, OTP platforms, and notification services

  • API keys & sender IDs
  • Delivery reports
  • Path to SMPP

What you can build

01

Send SMS

Outbound traffic with sender IDs configured in Messaging — DLT / compliance as applicable in India.

02

Reporting

Delivery and usage visibility in the portal, aligned with wallets and plan quotas.

03

Two-way patterns

Inbound / two-way SMS where your account and short/long codes support it.

Quick start

  1. 01

    Open Messaging

    Confirm sender IDs and entity/template registrations required for your traffic class.

  2. 02

    Create an API key

    Generate credentials in the Messaging portal; scope keys per app where possible.

  3. 03

    Send a test message

    Hit the SMS send endpoint with a registered sender and a small test payload.

  4. 04

    Subscribe to DLR webhooks

    Prefer push delivery receipts over polling — see Webhooks.

Auth

Credentials from your console

API keys live in the Messaging portal. Rotate keys if exposed. Live base URL and payload fields are confirmed in-console — samples below are illustrative only.

Illustrative send (shape only)

http
POST /v1/sms/messages
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json

{
  "to": ["9198XXXXXXXX"],
  "from": "SENDER",
  "body": "Your verification code is 482913",
  "dlt_template_id": "<if_required>"
}

# Confirm field names and DLT requirements for your traffic.

Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.

Common use cases

OTP & alerts

Auth codes, appointment reminders, and transactional notices from your app.

Fallback from WhatsApp

When chat isn’t available, drop to SMS from the same customer journey logic.

High-volume wholesale

If binds and routing policy are the product, evaluate Enterprise SMS (SMPP) instead of only REST.

  • SMPP is a separate enterprise track — see /smpp-platform.
  • Portal SMS packs and wallets are not the same as negotiated SMPP rate cards.

FAQs

SMS API — FAQs

Integration basics, credentials, and how this API relates to the product console.

Talk to sales

The Messaging portal on your Azmarq account — alongside sender IDs and reports.

No. SMPP is a separate enterprise messaging track for wholesale/high-volume operators.

No — they’re illustrative shapes. Confirm live endpoints and DLT fields in your console docs.

Build on SMS

Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.

Customer feedback

Conversations that teams can actually operate

Honest notes from growth, CX, ops, and compliance teams running CTWA, WhatsApp, journeys, inbox, voice, AI, and enterprise SMS on Azmarq CPaaS.

Meta Business Partners

Google Partner · Carrier-connected India · ISO 27001 · SOC 2 Type II

Featured feedback · CTWA Ads

CTWA leads finally land in one place. Our team qualifies on WhatsApp instead of chasing form dumps across tools — then My CDP keeps the thread for journeys.
AR

Ananya R.

Performance Marketing Lead · D2C · Bengaluru

Why teams stay

  • WhatsApp-first ops with SMS, RCS, email & voice
  • India-ready journeys, DND timing & sender discipline
  • Inbox, CDP, and AI handoff in one CPaaS stage
  • Enterprise SMS (SMPP) when volume is the product
Customer Journeys
Journeys with DND-aware waits and WhatsApp + SMS fallbacks feel built for India — not a US playbook pasted on.

Vikram S.

Growth Manager · Edtech · Pune

Unified Inbox
Unified Inbox cut the tab chaos. Tickets, queues, and SLAs finally match how our contact center actually works.

Neha K.

Head of CX · BFSI · Mumbai

Enterprise SMS
We needed SMPP-grade volume without bolting on another vendor. Azmarq kept wholesale SMS next to our WhatsApp stack.

Rahul M.

Operations Director · Logistics · Delhi NCR

Trust & Security
Security reviews went smoother with ISO 27001, SOC 2 Type II, and clear localization answers. That mattered for sign-off.

Priya T.

IT Compliance · Healthcare · Hyderabad

AI Agent Studio
AI Agent Studio handles FAQs on CTWA traffic, then hands off cleanly. Humans only see conversations that need them.

Arjun P.

Product Owner · Marketplace · Chennai

My CDP
My CDP stopped our spreadsheet segment nightmare. Opt-ins and attributes stay with the contact when we broadcast or drip.

Sana M.

CRM Lead · Retail · Ahmedabad

Voice 360
Voice callbacks after WhatsApp go quiet closed more high-intent leads than another SMS blast. Same profile, same journey.

Karan D.

Sales Ops · Real Estate · Noida

Messaging (SMS)
Messaging SMS for OTPs and alerts sits in the same console as WhatsApp. Finance finally sees one wallet story.

Meera L.

Engineering Manager · Fintech · Gurugram