SMS & Messaging API
Send and receive SMS, MMS, RCS and WhatsApp through one REST API - on Dollu's 800+ direct operator connections, with delivery receipts you can trust.
800+
Direct operator connections
200+
Countries reachable
4
Channels, one API
What is SMS & Messaging API?
The Dollu Messaging API gives your application a single, well-documented interface for every message it needs to send: transactional SMS, MMS with images and files, rich RCS Business Messaging and WhatsApp Business messages. One POST /v2/messages call, one message object, one set of delivery-status webhooks and one invoice, regardless of channel. Set channel to sms and you are live in an afternoon; add rcs or whatsapp later without changing your integration or your reporting.
Because Dollu is a wholesale SMS carrier as well as a CPaaS provider, messages sent through the API travel over the same 800+ direct operator connections used by banks, marketplaces and other aggregators. Direct routes matter for SMS more than almost anything else: they preserve your sender ID, deliver in seconds rather than minutes, return genuine handset delivery receipts instead of upstream acknowledgements, and keep you clear of grey routes that get filtered or blocked without warning.
Two-way messaging is first-class. Provision long codes, short codes, toll-free SMS numbers or alphanumeric sender IDs from the API, point them at an inbound webhook and every reply, keyword or STOP is delivered to your application as JSON with the originating number and any media attached. Opt-out handling, quiet hours, DLT template registration for India, 10DLC campaign registration for the US and country-specific sender-ID rules are managed on the platform, so you comply by default rather than by memory.
For teams running messaging at scale we add message templates with variables, batch sends of up to 10,000 recipients per request, scheduled delivery, per-message and per-campaign analytics, sub-accounts with their own keys and spend limits for reseller or multi-tenant use, and searchable message logs with the full delivery timeline. SDKs for Node.js, Python, Java, Go, PHP and .NET, an OpenAPI specification and a sandbox with test numbers round it out.
CPaaS request and event flow: REST in, webhooks out.
Why choose Dollu for messaging api.
The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.
Deliverability you can measure
Direct operator connections return real handset DLRs and per-country delivery rates in the dashboard, so you know what arrived - not just what left our platform.
One integration, every channel
The same message object, webhooks and logs cover SMS, MMS, RCS and WhatsApp, with automatic fallback to SMS when a rich channel is unavailable on the handset.
Compliance without the paperwork
DLT entity and template registration, 10DLC brand and campaign vetting, opt-out lists and country sender-ID rules are handled on the platform and enforced before a message is sent.
Built for multi-tenant products
Sub-accounts with their own numbers, keys, spend caps and reporting let SaaS platforms and resellers offer messaging to their customers from a single Dollu contract.
Carrier pricing, API convenience
Per-message rates come from our wholesale deck rather than a marked-up reseller list, with volume tiers and no platform fee for the API itself.
Capabilities in detail.
Everything included with SMS & Messaging API - the platform features, options and controls you get from day one.
- 01
Outbound messaging
POST /v2/messages with to, from and text (or media URLs); automatic GSM-7/UCS-2 encoding detection, concatenation up to 10 segments, validity period, callback URL and client reference per message.
- 02
Inbound and two-way
Replies, keywords and MMS attachments arrive on your webhook as message.received; built-in STOP, START and HELP handling, auto-replies and conversation threading by number pair.
- 03
Delivery receipts and status
message.queued, sent, delivered, undelivered and failed webhooks with operator error codes; GET /v2/messages/{id} returns the full timeline including the operator that delivered it.
- 04
Rich channels: MMS, RCS, WhatsApp
MMS images and files in the US and Canada; RCS cards, carousels and suggested replies; approved WhatsApp templates and session messages - all with SMS fallback and unified status events.
- 05
Numbers and sender IDs
Search and buy SMS-enabled long codes, toll-free numbers and short codes with POST /v2/numbers; register alphanumeric sender IDs where the country permits; port existing numbers in.
- 06
Templates, batches and scheduling
Store templates with variables and versioning; POST /v2/messages/batch for up to 10,000 recipients with per-recipient substitutions; schedule delivery in the recipient's timezone.
- 07
Sub-accounts and access control
Create sub-accounts with isolated numbers, keys, webhooks and monthly spend limits; scoped keys (send-only, read-only), IP allow-lists and SSO for the console.
- 08
Analytics and logs
Delivery, latency and cost by country, operator, sender and campaign; 90-day searchable logs; CSV and API export; threshold alerts on delivery-rate drops.
- 09
Compliance tooling
DLT and 10DLC registration workflows, opt-out and suppression lists, quiet-hours enforcement, content filtering for regulated destinations and audit trails for every consent change.
How it works.
From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.
- Step 01
Create an account and key
Sign up, generate a scoped API key and install an SDK. The sandbox lets you send to test numbers and receive simulated delivery receipts and inbound replies immediately.
- Step 02
Choose a sender
Buy a long code or toll-free number, register an alphanumeric sender ID or apply for a short code from the console. We handle DLT, 10DLC and country registrations with you.
- Step 03
Send and receive
Call POST /v2/messages, set a webhook for status and inbound events and handle message.delivered and message.received. Add templates and batches as volume grows.
- Step 04
Add channels and scale
Enable RCS and WhatsApp on the same integration, raise throughput with your account manager, create sub-accounts for customers or brands and monitor delivery per operator.
Who uses this and why.
Typical deployments across carriers, enterprises, platforms and contact centres.
Transactional alerts and notifications
Order confirmations, account alerts, appointment reminders and one-time codes delivered in seconds with per-message status you can show in your own UI.
Customer conversations
Two-way support and sales conversations over SMS, RCS or WhatsApp, threaded by number and routed to your CRM or help-desk via inbound webhooks.
Marketing campaigns
Promotions and re-engagement with templates, scheduling, opt-out enforcement and campaign-level analytics - on compliant registered senders.
Logistics and delivery updates
Dispatch, ETA and proof-of-delivery messages with driver-customer replies, MMS photos and location links across every country you ship to.
SaaS platforms and resellers
Embed messaging in your product with sub-accounts, white-label reporting and wholesale-derived pricing that leaves room for your own margin.
Technical & commercial specifications.
Key parameters at a glance. Ask us for the full service description and SLA document.
| API | REST/JSON at api.dollu.com/v2/messages; OpenAPI 3.1; SMPP v3.4 for high volume |
|---|---|
| Channels | SMS, MMS (US/CA), RCS Business Messaging, WhatsApp Business |
| Coverage | 200+ countries and territories; 800+ direct operator connections |
| Sender types | Long codes, short codes, toll-free, alphanumeric sender IDs |
| Throughput | 100 msg/s per account by default; short codes 500+ msg/s; higher on request |
| Webhooks | message.received, sent, delivered, undelivered, failed; HMAC-SHA256 signed |
| Encoding | GSM-7 and UCS-2 auto-detected; concatenation up to 10 segments |
| SDKs | Node.js, Python, Java, Go, PHP, .NET |
| Compliance | DLT (India), 10DLC and TCPA (US), GDPR, opt-out management |
| Billing | Per segment or per message by destination; prepaid or monthly; USD/EUR/GBP/INR |
How APIs / CPaaS are priced.
APIs are usage-based: per minute, per message, per verification, per participant-minute or per email - at carrier pricing, because Dollu’s own network sits underneath the endpoints.
We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.
- Free sandbox for development and testing
- Sub-account and reseller rate decks
- Committed-spend discounts by monthly usage
- No platform fee at entry volumes
- Numbers added at rental + usage
- Billing
- Metered per unit; prepaid balance or postpaid invoicing; usage visible in real time in the portal and API
- Commitment
- None; committed monthly spend earns tiered discounts
Messaging API - your questions answered.
The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.
Still have a question?
Ask our solutions teamRelated services.
Services customers commonly combine with SMS & Messaging API.
Send your first message today.
Get a sandbox key and send to a test number in minutes, then talk to [email protected] about routes, sender registration and volume pricing for your destinations.
