One unified API for SMS, messengers and flash calls. Sandbox access, documented endpoints, Postman collections and webhooks — designed for engineers shipping at scale.
No SDK to install. Any HTTP client will do. Use the curl snippet to verify your key, then swap in your stack.
Register on the developer portal — fill in company, work email, and your use case.
Open registration →A Massiva admin reviews your request and issues a scoped API key (OMNI, Broadcast, Recipients).
Auth guide →Call POST /api/v1/messages with the key in the X-API-Key header. Track delivery via webhooks or EDRs.
OMNI reference →curl -X POST https://client.massiva.com/api/v1/messages \
-H "X-API-Key: $MASSIVA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"contact": "905063565285",
"channel": 1,
"senderId": "MASSIVA",
"payload": { "text": "Hello from Massiva" }
}'Returns messageId plus a delivery webhook to your registered URL. See delivery statuses and webhook reference.
/api/v1/messagesSingle endpoint to send across SMS, WhatsApp, Viber, RCS, Telegram, Email, Push, TTS and WeChat.
/api/v1/broadcastsSchedule mass campaigns, manage templates and target audiences with detailed delivery reports.
/api/v1/recipientsContact directory with attributes, tags, segments and reusable filter expressions.
/api/v1/paymentsBackOffice payments, balance top-ups and invoicing with X-Private-Token authentication.
Use the same POST /messages endpoint — the channel integer selects transport.
Channels, senders, templates, EDRs, messages, omnimessages, Telegram Gateway verify/revoke.
Campaign management, contact directory, and BackOffice payments — single Postman collection.
Bash scripts for the most common flows: send SMS, WhatsApp template, RCS, fallback, OTP, EDRs.
Reference clients, webhook receivers, OpenAPI specs and Postman collections live in the open. Star, fork, or open a pull request.
Request developer access. Once approved you get a sandbox API key and full documentation for OMNI, Broadcast, Recipients and Payments.