Send SMS to Jordan
from $0.0280/msg

import os, requests

resp = requests.post(
    "https://api.smsroute.cc/v1/messages",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+9625551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.json())

curl -X POST https://api.smsroute.cc/v1/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+9625551234567",
    "from": "smsroute",
    "text": "Your verification code is 384921"
  }'

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9625551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+9625551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/v1/messages",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+9625551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/v1/messages');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);

Mobile Operators in Jordan: Zain, Umniah, and Orange

Jordan has 11 million mobile subscribers with 142% penetration (multi-SIM adoption is common in the region). All three operators use the 7XX XXX XXX prefix after the country code +962. smsroute.cc delivers to all three operators simultaneously. The 97.9% delivery success rate reflects direct interconnect with each operator's SMS gateway.

Mobile Operators in Jordan: Zain, Umniah, and Orange

Jordan has 11 million mobile subscribers with 142% penetration (multi-SIM adoption is common in the region). All three operators use the 7XX XXX XXX prefix after the country code +962. smsroute.cc delivers to all three operators simultaneously. The 97.9% delivery success rate reflects direct interconnect with each operator's SMS gateway.

Pricing Comparison: smsroute.cc vs. Twilio, Vonage, and Others

smsroute.cc is 60% cheaper than Twilio for Jordan SMS. On a 100,000-message campaign, you save $4,200 ($2,800 with smsroute.cc vs. $7,000 with Twilio). All competitors listed above require identity verification and support traditional payment methods (cards, bank transfers). smsroute.cc requires only a crypto wallet and no KYC.

Pricing Comparison: smsroute.cc vs. Twilio, Vonage, and Others

smsroute.cc is 60% cheaper than Twilio for Jordan SMS. On a 100,000-message campaign, you save $4,200 ($2,800 with smsroute.cc vs. $7,000 with Twilio). All competitors listed above require identity verification and support traditional payment methods (cards, bank transfers). smsroute.cc requires only a crypto wallet and no KYC.

Latency and Delivery Guarantees

Median Latency (p50): 145 milliseconds. This means half of all SMS reach the recipient in 145 ms or faster.

95th Percentile Latency (p95): 300 milliseconds. 95% of SMS are delivered within 300 ms.

Delivery Success Rate: 97.9%. This reflects the percentage of SMS that reach the recipient's handset without bouncing or expiring. Failures are primarily due to invalid numbers, switched-off devices, or network-layer congestion from the recipient's operator.

Uptime: 99.9%. smsroute.cc's infrastructure is geographically distributed across multiple regions with redundant gateways. Maintenance windows are announced in advance on our status page.

Tier-1 Delivery: 99%. We maintain direct peering agreements with Zain, Umniah, and Orange. SMS are routed directly to operator gateways without intermediaries, ensuring first-attempt delivery.

Latency varies based on operator load, time of day, and message content. Marketing SMS during busy hours (08:00–14:00 EET, weekdays) may see higher latencies. Transactional SMS (OTP, alerts) are prioritized and typically deliver in under 100 ms.

Latency and Delivery Guarantees

Median Latency (p50): 145 milliseconds. This means half of all SMS reach the recipient in 145 ms or faster.

95th Percentile Latency (p95): 300 milliseconds. 95% of SMS are delivered within 300 ms.

Delivery Success Rate: 97.9%. This reflects the percentage of SMS that reach the recipient's handset without bouncing or expiring. Failures are primarily due to invalid numbers, switched-off devices, or network-layer congestion from the recipient's operator.

Uptime: 99.9%. smsroute.cc's infrastructure is geographically distributed across multiple regions with redundant gateways. Maintenance windows are announced in advance on our status page.

Tier-1 Delivery: 99%. We maintain direct peering agreements with Zain, Umniah, and Orange. SMS are routed directly to operator gateways without intermediaries, ensuring first-attempt delivery.

Latency varies based on operator load, time of day, and message content. Marketing SMS during busy hours (08:00–14:00 EET, weekdays) may see higher latencies. Transactional SMS (OTP, alerts) are prioritized and typically deliver in under 100 ms.

Jordanian Consent Framework and TRA Regulations

Jordan's Telecommunications Law 40/2002, administered by the Telecommunications Regulatory Authority (TRA) at https://www.trc.gov.jo/, mandates explicit opt-in consent for marketing SMS. This is stricter than soft opt-in (implied consent at purchase). Before sending promotional content, you must collect affirmative written or digital agreement from the recipient.

Transactional SMS—including one-time passwords (OTP), payment confirmations, account alerts, and appointment reminders—do not require pre-consent. These are essential business communications and can be sent to opted-out recipients. However, if a recipient opts out from transactional messaging, you must honor their request immediately.

The TRA publishes enforcement guidance and has taken action against major senders for consent violations, false sender identification, and breach of quiet hours. Document your consent process: timestamps, IP addresses, and the exact language of the opt-in. If challenged, you must prove explicit agreement.

smsroute.cc does not provide consent management or list scrubbing. You are responsible for maintaining opt-in records. We enforce quiet hours server-side (see below) but will not block messages you attempt to send outside compliance windows; we recommend building compliance checks into your application layer.

Jordanian Consent Framework and TRA Regulations

Jordan's Telecommunications Law 40/2002, administered by the Telecommunications Regulatory Authority (TRA) at https://www.trc.gov.jo/, mandates explicit opt-in consent for marketing SMS. This is stricter than soft opt-in (implied consent at purchase). Before sending promotional content, you must collect affirmative written or digital agreement from the recipient.

Transactional SMS—including one-time passwords (OTP), payment confirmations, account alerts, and appointment reminders—do not require pre-consent. These are essential business communications and can be sent to opted-out recipients. However, if a recipient opts out from transactional messaging, you must honor their request immediately.

The TRA publishes enforcement guidance and has taken action against major senders for consent violations, false sender identification, and breach of quiet hours. Document your consent process: timestamps, IP addresses, and the exact language of the opt-in. If challenged, you must prove explicit agreement.

smsroute.cc does not provide consent management or list scrubbing. You are responsible for maintaining opt-in records. We enforce quiet hours server-side (see below) but will not block messages you attempt to send outside compliance windows; we recommend building compliance checks into your application layer.

Frequently Asked Questions

Frequently Asked Questions

Related