Developers · Verification
Verification traffic across SMS, email, and voice
Send one-time passwords and verification messages using Azmarq Messaging (SMS), transactional Email, and Voice where enabled — with reporting and wallet/plan controls.
Built for: Auth, fintech, and app security teams
- SMS OTP
- Email codes
- Voice OTP option
What you can build
01
SMS verification
Use Messaging API keys and sender IDs for OTP-style traffic with DLT discipline where required.
02
Email transactional codes
Email API for mailbox-based verification and security notices.
03
Voice option
Voice 360 can speak codes when SMS delivery isn’t reliable for the user.
Quick start
01
Pick primary + fallback channel
Most teams lead with SMS, add email, and keep voice as tertiary.
02
Create channel credentials
Keys for Messaging and/or Email; confirm Voice entitlements if needed.
03
Implement generate → send → verify
Keep OTP generation and validation in your app; Azmarq delivers the message.
04
Watch DLR / bounce events
Use webhooks to detect failed delivery and trigger fallback channels.
Auth
Credentials from your console
OTP logic (generation, expiry, attempt limits) stays in your application. Azmarq APIs deliver the message. Confirm templates and rate limits with your account.
Illustrative SMS OTP send (shape only)
httpPOST /v1/sms/messages
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json
{
"to": ["9198XXXXXXXX"],
"from": "SENDER",
"body": "Your Azmarq demo code is 482913. Valid for 5 minutes."
}
# Prefer dedicated OTP templates / DLT IDs where required.
# Fallback: Email API or Voice API on delivery failure.Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.
Common use cases
Login & signup
Phone or email verification at account creation.
Step-up auth
Confirm high-risk actions with a second factor message.
Retry across channels
SMS fail → email or voice using the same verification code lifecycle.
FAQs
OTP API — FAQs
Integration basics, credentials, and how this API relates to the product console.
Talk to salesYour app should generate, expire, and validate codes. Azmarq APIs deliver the message on SMS, email, or voice.
Most teams lead with SMS, add email, and keep voice as fallback when SMS fails.
Build on Verification
Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.
