This API is for international destinations. SMS to Indian numbers goes through a different
API on a different host, because Indian traffic carries DLT registration fields — see
Send SMS — India.
Endpoint
string
required
application/jsonAuthentication
Authentication is akey value inside the JSON request body — not an HTTP header. This is
the main difference integrators trip over when moving between the two SMS APIs.
string
required
API key assigned to your account.
How it compares to India SMS
Tracking your own reference IDs
Every message can carry your own identifier, echoed back on both the submission response and the delivery receipt. There are two independent mechanisms — use either, or both — see Reference IDs.
Either is returned whenever you send it, on success and failure alike.
Coverage
OneXtel carries international SMS to destinations worldwide. There is no published country list — confirm a specific destination, and its commercial terms, with your account team before you build against it.Destination obligations
Requirements vary sharply by country, and several put an obligation on you rather than on OneXtel. Two common examples:
This matters more than it looks, because OneXtel does not validate the
from field — an
unregistered sender ID submits cleanly and fails downstream. See
Sender IDs.
Others apply elsewhere. There is no consolidated list — check the destinations you intend to send
to with your account team, early, because registration can take longer than the integration does.
Testing
There is no sandbox environment and no test key — integrate against your live API key.Anything you send while integrating is a real message on a live route. Send only to numbers you
control, and keep test volumes small.
Endpoints at a glance
Next steps
- Send SMS — payloads, reference IDs, and responses
- DLR callback — the receipt posted to your URL
- Error codes — what each
ERRORCODEmeans