API Reference
  1. SMS API
  2. Message Sending

Send SMS (Secured)

get
https://api.rmlconnect.net/bulksms/bulksms

Submits a single SMS or a batch of SMS messages for delivery over HTTPS.
Available on both port 443 and port 8443.

Long messages: Messages exceeding standard length are automatically split
and reassembled on the recipient device. Billing is per segment:

  • Plain text: 153 characters per segment
  • Unicode: 268 characters per segment

Bulk response format (multiple destinations):

<Error_Code>|<destination>|<message_id>,<Error_Code>|<destination>|<message_id>,...

Mid-batch abort scenarios:

  • If any error other than an invalid destination occurs, the batch is aborted immediately.
  • If credits are exhausted mid-batch, processing stops and 1025|<last_destination> is appended.

Retry Policy: Do NOT retry for any error code except 1709.
For 1715, do not re-submit the same message.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
required

Account username.

password
required

Account password.

integer
enum
required
Defaults to 0

Message encoding type.

  • 0 — Plain Text (GSM 3.38)
  • 1 — Flash Message (GSM 3.38)
  • 2 — Unicode (message must be UTF-16BE hex encoded)
  • 3 — Reserved
  • 4 — WAP Push (use the url parameter for the link)
  • 5 — Plain Text (ISO-8859-1)
  • 6 — Unicode Flash (message must be UTF-16BE hex encoded)
  • 7 — Flash Message (ISO-8859-1)
integer
enum
required
Defaults to 1

Delivery report flag. 1 = enable, 0 = disable.

Allowed:
string
required

Destination MSISDN(s). May include or omit the + prefix (URL-encode + as %2B).
For multiple destinations, separate with commas (URL-encode commas as %2C).

string
required
length ≤ 18

Sender ID displayed to the recipient.

  • Max 18 characters if numeric only
  • Max 11 characters if alphanumeric

To prefix a + sign, include it URL-encoded as %2B. Additional restrictions
may be enforced by the SMSC.

string
required

Message content, URL-encoded (UTF-8).
For Unicode messages (type=2 or type=6), encode content in UTF-16BE hex format.
For WAP Push (type=4), this is the display text of the push message.

string

WAP Push link URL. Required when type=4, ignored for all other message types.
Must be URL-encoded (UTF-8).

Responses

400

Bad request / missing parameters.

401

Authentication failure.

500

Internal server error. Please contact support if this persists.

Updated 7 days ago

Did this page help you?
Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain

Updated 7 days ago

Did this page help you?