Build on the SMSwarriors API.

Send your first message in three steps.

curl -L "https://<your-api-host>/bulk/sendsms" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "type": "text",
    "auth": { "username": "your_username", "password": "your_password" },
    "sender": "SMSwarriors",
    "receiver": "4179123456",
    "dcs": "GSM",
    "text": "Hello from SMSwarriors!",
    "dlrMask": 19,
    "dlrUrl": "https://your-app.com/dlr-callback"
  }'

{
  "msgId": "9325d0a8-2638-11e6-afe7-bffc7cc8fa4f",
  "numParts": 1
}

Username & password, in the request body.

There's no separate API key or OAuth flow. Every request carries an auth object with the username and password issued to your account. Always send requests over HTTPS so credentials stay encrypted in transit.

"auth": {
  "username": "your_username",
  "password": "your_password"
}

Send one JSON object per request. The same endpoint handles single messages and each message in a bulk job — call it once per recipient, or fan requests out from your own queue. There are three message types: GSM-encoded text, Unicode text, and WAP Service Indication (WSI) links — pick the one you need with type and dcs.

Common parameters

Text message fields

CONTENT='{
  "type": "text",
  "auth": {"username": "your_username", "password": "your_password"},
  "sender": "SMSwarriors",
  "receiver": "4179123456",
  "dcs": "GSM",
  "text": "This is a test message",
  "dlrMask": 19,
  "dlrUrl": "https://your-app.com/dlr-callback"
}'

curl -L "https://<your-api-host>/bulk/sendsms" \
  -H "Content-Type: application/json" \
  -X POST -d "$CONTENT"

const res = await fetch("https://<your-api-host>/bulk/sendsms", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    type: "text",
    auth: { username: "your_username", password: "your_password" },
    sender: "SMSwarriors",
    receiver: "4179123456",
    dcs: "GSM",
    text: "This is a test message",
    dlrMask: 19,
    dlrUrl: "https://your-app.com/dlr-callback",
  }),
});

const data = await res.json();
console.log(data.msgId, data.numParts);

$payload = json_encode([
    "type" => "text",
    "auth" => ["username" => "your_username", "password" => "your_password"],
    "sender" => "SMSwarriors",
    "receiver" => "4179123456",
    "dcs" => "GSM",
    "text" => "This is a test message",
    "dlrMask" => 19,
    "dlrUrl" => "https://your-app.com/dlr-callback",
]);

$ch = curl_init("https://<your-api-host>/bulk/sendsms");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_POSTFIELDS => $payload,
    CURLOPT_HTTPHEADER => ["Content-Type: application/json"],
    CURLOPT_RETURNTRANSFER => true,
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

{
  "type": "text",
  "auth": {"username": "your_username", "password": "your_password"},
  "sender": "SMSwarriors",
  "receiver": "4179123456",
  "dcs": "UCS",
  "text": "Message with UTF-8 characters üöä€ 你好",
  "dlrMask": 19,
  "dlrUrl": "https://your-app.com/dlr-callback"
}

Sending a WSI (WAP Service Indication).

A WSI delivers a clickable link with a title, rendered natively by the handset — useful for one-tap links in place of a plain-text URL. Use the same endpoint with type: "wsi".

{
  "type": "wsi",
  "auth": {"username": "your_username", "password": "your_password"},
  "sender": "SMSwarriors",
  "receiver": "41787078880",
  "url": "https://smswarriors.com/",
  "title": "SMSwarriors",
  "dlrMask": 19,
  "dlrUrl": "https://your-app.com/dlr-callback"
}

What comes back from the submission call.

{
  "msgId": "9325d0a8-2638-11e6-afe7-bffc7cc8fa4f",
  "numParts": 2
}

{
  "error": {
    "code": "107",
    "message": "Invalid sender"
  }
}

Submission error codes.

Returned in the error.code field of a 420 response.

If you set dlrUrl on submission, we POST a JSON delivery report to that URL as the message moves through the network — from acceptance by the carrier through to the handset (or failure).

Message lifecycle

Every message resolves to one of four outcomes. Each has its own reasons and its own timing.

DLR events & mask

Choose which events you want with dlrMask — add the values together. Default is 19 (Delivered + Undelivered + Rejected — the three final states).

Callback payload

{
  "msgId": "9325d0a8-2638-11e6-afe7-bffc7cc8fa4f",
  "event": "DELIVERED",
  "errorCode": 0,
  "errorMessage": "",
  "partNum": 0,
  "numParts": 1,
  "accountName": "your_username",
  "sendTime": 0,
  "dlrTime": 2,
  "custom": {}
}

DLR error codes

Full list — most of these come straight from the mobile network (HLR/MSC/SGSN-level failures); the ones above 500 are gateway-level.

Character limits & long-message concatenation.

Messages longer than one segment are split automatically — no extra work required — but part count affects billing, so it's worth knowing the limits.

Sender ID character support (alphanumeric)

Letters and digits (0–9, a–z, A–Z) are always supported. Beyond that, only the special characters below are allowed in an alphanumeric sender ID.

Throttling & retries.

Submitting faster than your account's allowed rate returns error 105 — RC_THROTTLING_ERROR. This is the one rejection that's safe to retry automatically.