API Reference
  1. SMS API
  2. Nigeria Enterprise
  3. Scheduling

Schedule SMS for future delivery

get
https://ngn.rmlconnect.net:8443/bulksms/schedulemsg

Submits a message to be delivered at a specified future date and time,
relative to a specified timezone offset (gmt).

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

HTTP account username issued by Route Mobile.

password
required

HTTP account password.

string
required

Message content, URL encoded using UTF-8. For Unicode message types
(2, 6), the content must additionally be hex-encoded in UTF-16BE
format before URL encoding.

string
required

Destination mobile number(s), with or without a leading +. Multiple
numbers are comma-separated (URL-encode the comma).

integer
enum
required

Message type / character encoding for the scheduled message:

  • 0: Text
  • 1: Flash
  • 2: Unicode
  • 3: Binary
  • 4: WAP
  • 6: Unicode-Flash
Allowed:
integer
enum
Defaults to 1

Whether a delivery report is required. 0 = not required, 1 = required. Defaults to 1 if omitted.

Allowed:
string

Landing page link, used only when type=4 (WAP Push). Not required for
any other message type; if supplied for other types, it is ignored.

string
required
length ≤ 18

Sender ID displayed to the recipient. Maximum length is 18 characters if
numeric, or 11 characters if alphanumeric. Additional restrictions may
be enforced by the destination carrier.

string
required
^\d{2}/\d{2}/\d{4}$

Date on which the message should be sent, in MM/DD/YYYY format
(for example, 03/03/2013).

string
required
^\d{2}:\d{2} (am|pm)$

Time at which the message should be sent, in hh:mm am/pm format
(for example, 03:45 am or 11:51 pm).

string
required

Timezone offset for the schedule date/time, for example +5:30,
-10:00, or GMT +5:30.

Responses

400

Malformed request - for example, a required parameter is missing.

401

Reserved for transport-level authentication failures. Account-level
authentication issues are returned as a 1703 code in the 200
response body rather than an HTTP 401.

500

Internal server/gateway error at the transport level.

Updated 8 days ago

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

Updated 8 days ago

Did this page help you?