Send Bulk SMS (Instant)

Submits an SMS for immediate delivery to one or more destination numbers
using Reseller-tier credentials.

Authentication: Query-parameter based — username + password in
the query string. No additional headers or tokens required.


Example Request (from your listed URL):

GET https://rslr.connectbind.com:8443/bulksms/bulksms
  ?username=xxxxxx
  &password=*******
  &type=0
  &dlr=1
  &destination=xxxx
  &source=xxx
  &message=Testing

Success Response Format (plain text):

1701|<CELL_NO>|<MESSAGE_ID>

The MESSAGE_ID can later be used to map delivery reports back to this submission.

Multi-Destination Reply Format:

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

Exceptional Situations:

  • If a request has multiple destinations and an error other than "Invalid
    Destination" occurs, the whole batch is aborted immediately.
  • If "Invalid Destination" occurs for one number in a batch, that number is
    skipped and the rest of the batch proceeds.
  • If the SMPP server goes down mid-request, the API retries a fixed number
    of times (10ms gap between retries). If retries exhaust, the batch aborts
    at that destination and returns 1709|<destination_at_which_batch_aborted>
    appended to the partial results.
  • If credits run out mid-batch, the batch aborts at that destination and
    returns 1025|<destination_at_which_batch_aborted> appended to the
    partial results.

Retry Guidance:

Apart from error 1709, do not retry re-sending the message for any
other error code (including standard SMPP v3.4 error codes, which may
also be returned where applicable).

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

Reseller account username (SMPP account username).

password
required

Reseller account password. Treat as a secret — never log or expose.

integer
enum
required

Message encoding type.

ValueDescription
0Plain Text (GSM 03.38 character encoding)
1Flash Message (GSM 03.38 character encoding)
2Unicode (message content must be in Hex / UTF-16BE)
3Reserved
4WAP Push (requires url parameter)
5Plain Text (ISO-8859-1 character encoding)
6Unicode Flash (message content must be in Hex / UTF-16BE)
7Flash Message (ISO-8859-1 character encoding)
integer
enum
required

Whether a delivery report is required for this message.

ValueMeaning
0No delivery report required
1Delivery report required
Allowed:
string
required

Mobile number to send the message to. May or may not include a +
prefix. Multiple numbers can be comma-separated — note the comma
itself must be URL-encoded (%2C) in the raw query string.

If a + is used, it must also be URL-encoded as %2B.

string
required

The sender/source address to appear on the recipient's device.

  • Max length 18 if purely numeric
  • Max length 11 if alphanumeric
  • Additional restrictions may be enforced by the destination SMSC/operator

To prefix a + sign so it displays on the handset, URL-encode it as
%2B in the source value itself.

string
required

The message content to send. Must be URL-UTF-8 encoded.

Length / concatenation rules:

  • Plain text: up to 160 characters as a single segment; for longer
    ("long") messages, concatenation is billed at 153 characters per
    segment
    (the remaining characters per segment are used internally
    for re-assembly headers).
  • Flash: up to 140 characters per segment.
  • Unicode: up to 280 characters as a single segment; long Unicode
    messages are billed at 268 characters per segment.

Encoding by type:

  • type=0,1,5,7: send message as plain URL-encoded text.
  • type=2,6 (Unicode / Unicode Flash): message must be converted to
    UTF-16BE hex before sending. Example: "Demo Message!!!" encodes
    to 00440065006D006F0020004D0065007300730061006700650021002100210
    in this format.
  • type=4 (WAP Push): this field holds the display text shown in
    the push notification, not the link itself (the link goes in url).
uri

Required only when type=4 (WAP Push) — holds the link to be pushed.
For all other types, leave empty; if supplied anyway, it is ignored.
Must be URL-encoded with UTF-8 (including for non-ASCII domain names).

Responses

400

Bad request — one or more required parameters missing.

401

Authentication failure.

500

Internal server error. Contact support if this persists.

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