A2P SMS on direct operator routes.
Send A2P, two-way and bulk SMS through one REST API with real delivery receipts on every message. Direct operator connections, no grey hops, sold under your brand.
- A2P SMS
- Two-way
- Delivery receipts
- AI routing
POST /v1/messages { "to": "+44 7700 900123", "from": "ACME", "text": "Your code is 482 913" }
- Submitted0 ms
- Routed · direct operator38 ms
- Delivered · handset receipt1.2 s
AI in SMS API, working on its own.
AI that takes the action, not just the note. Running inside the network, on your brand. See SMS inside the AceEX business phone.
AI route selection
AI watches delivery results and shifts traffic to the best direct route when one slows down.
Reply understanding
Inbound replies are read for intent, so “STOP”, “yes” or a question triggers the right action.
Send-time optimization
AI schedules bulk sends for when each recipient is most likely to read the message.
SMS API, feature by feature.
- Single send endpoint
Send any message with POST /v1/messages and a few fields.
- Two-way SMS
Receive replies on long codes or short codes via webhook.
- Bulk campaigns
Send from OTP bursts to national campaigns at steady throughput.
- Real delivery receipts
Get handset-level status on every message, not just submission.
- Unicode and concatenation
Send long and local-script messages with automatic segment handling.
- Sender management
Manage sender IDs per enterprise so messages arrive from a trusted name.
What enterprises send with it.
From OTP bursts to national campaigns, the same endpoint carries every kind of message. See retail and eCommerce solutions.
Know what happened to every message.
Real receipts mean handset-level status, not just “accepted”. Every state change reaches your enterprise by webhook, and the live dashboard shows the same picture. Check live platform status.
- 1submitted
Your API accepted the message and queued it for sending.
- 2routed
It left on a direct operator route, chosen for completion.
- 3delivered
The handset confirmed receipt, with a timestamp.
- 4undelivered
The operator reported a failure, so the receipt carries the reason.
- 5replied
A two-way reply arrived on your long code or short code.
{
"id": "msg_8f2a…",
"status": "delivered",
"route": "direct-operator",
"to": "+44 7700 900123",
"segments": 1,
"encoding": "GSM-7",
"delivered_at": "2026-10-02T09:41:03Z",
"error": null
}Illustrative payload
From setup to live.
- 01Sign up
Enterprises open an account on your branded portal.
- 02Register senders
Set up sender IDs so messages get delivered and recognized.
- 03Send
Call POST /v1/messages from any language or SDK.
- 04Track
Watch receipts and usage in real time on the dashboard.
Track feeds back into Send: receipts and usage tune the next batch.
We supply the APIs, docs, sandbox, portal and billing under your name. You supply the customers.
See the reseller programOne API for voice, messaging and AI agents, on direct routes.
Read the API referenceSMS is one channel. Add the rest.
Questions, answered.
Messages travel on direct operator connections, so receipts are real and delivery is predictable.
Yes. The platform handles everything from OTP bursts to national campaigns.
Yes. Two-way SMS delivers replies on long codes or short codes to your webhook.
Unicode and concatenation are automatic. Long messages are split into segments and local scripts are encoded correctly.
Yes. Sender IDs are managed per enterprise so messages arrive from a trusted name.
Give your enterprises an API.
Book a 30-minute technical briefing with our engineers.