International SMS Overview

Base URL, authentication, reference IDs, and endpoint summary for the OneXtel International SMS List API.

The SMS List API delivers SMS to destinations outside India through the OneX Global platform. You submit message details as JSON and the platform forwards them to the recipients.

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

POST https://api.int.onexglobal.io/api/jsmslist

Content-Type · string · required

application/json

Authentication

Authentication is a key 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.

key · string · required

API key assigned to your account.

How it compares to India SMS

	International	India
Host	api.int.onexglobal.io	api.onexaura.com
Path	/api/jsmslist	/send_sms
Authentication	key in the body	apikey header
Message array	listsms	sms
Batching	Up to 2,500 per request	Many messages per request
DLT fields (templateId, entityId)	Not used	Required
DLR field style	UPPERCASE	camelCase

The two APIs are not interchangeable. Check which one your account is provisioned for before you build.

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.

Field	Count	Echoed back in
clientsmsid	One	Submission response, and DLR as CLIENTMSID
custref1–custref5	Up to five	Submission response and DLR, under the same names

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:

Destination	What it requires
UAE	Sender ID registration before traffic is accepted
USA	A2P 10DLC registration of brand and campaign

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

Endpoint	Method	Purpose
/api/jsmslist	POST	Submit one or more SMS messages
DLR callback	POST (inbound, to your URL)	Receive the final delivery state

Next steps

• Send SMS — payloads, reference IDs, and responses
• DLR callback — the receipt posted to your URL
• Error codes — what each ERRORCODE means