Send SMS to Yemen
from $0.0550/msg

smsroute.cc is a crypto-only A2P SMS gateway to Yemen covering 18 million subscribers across Houthi-aligned operators (55%), Saba Telecom (30%), and Walid Telecom (15%). Price: $0.0550/message (30% below Twilio at $0.0786). Median latency: 420 ms. Delivery success: 82.3%. No KYC at signup—pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. $5 minimum top-up.

Why Arabic SMS Segments Cut Your Yemen Character Budget in Half

Arabic script—the primary language in Yemen—triggers UCS-2 encoding in mobile networks. UCS-2 encodes each character as a two-byte unit, reducing the character capacity of a single SMS segment from 160 characters (GSM-7 for English) to 70 characters. A typical English message that fits in one segment may require two or three segments in Arabic, doubling or tripling your per-message cost.

Example: The Arabic phrase "مرحبا بك في النظام" (Welcome to the system) is 18 characters in length. In GSM-7 encoding, this would occupy just one segment, consuming 1 SMS credit. Under UCS-2, the same message still occupies one segment (18 × 2 bytes = 36 bytes, well within the 140-byte UCS-2 limit). However, a longer Arabic message of 85 characters—such as a customer notification or promotional message—would overflow into a second segment, consuming 2 SMS credits instead of 1.

smsroute.cc's API transparently handles UCS-2 segmentation: the platform detects Arabic (and other non-Latin scripts) automatically and reports the true segment count in delivery receipts. Operators in Yemen bill based on actual segment transmission, not character count. Plan your campaign budget accordingly: allocate 2–3× the SMS volume if your content is primarily Arabic or mixed-script. For transactional SMS (OTP, account alerts), brevity is both a compliance best practice and a cost optimization strategy.

GSM-7 vs. UCS-2 Encoding and Operator Reach

Yemen's three major operators—Houthi-aligned operators (Yemen Mobile), Saba Telecom, and Walid Telecom—all support UCS-2 encoding natively. This means Arabic-language SMS, emojis, and any Unicode character can be transmitted without loss or corruption. However, operator support for international A2P (application-to-person) messaging remains inconsistent due to the civil conflict and international sanctions.

GSM-7 encoding remains the lowest-cost option for Latin-script SMS (English, French, etc.) and supports a 160-character segment limit. If your message is entirely in English or uses only ASCII characters, GSM-7 is applied, and your segment count is lower. Mixed-script messages (e.g., "Your code is 123456. كودك هو") will trigger UCS-2 encoding for the entire message.

Operator interconnect with international gateways is highly unreliable in Yemen. During periods of conflict escalation or sanction enforcement, carrier routing may degrade or become unavailable. smsroute.cc maintains partnerships with tier-1 telecom providers that have negotiated access; however, delivery success is capped at 82.3% due to the fragmented routing environment and sanctions-related blocks.

Consent Framework and Regulatory Compliance

Yemen has de facto no functional consent framework. The National Telecommunications Commission (NTC; https://www.ntc.gov.ye/) is the nominal regulator; however, in Houthi-controlled territory, de facto regulation is exercised by Houthi-aligned operators themselves. In Saba-controlled and internationally recognized government areas, regulatory guidance is sparse and uneven.

Key points:

• No opt-in statute: Yemen has no equivalent to GDPR, CCPA, PDPA, or TCPA. Soft opt-in (consent implied through prior commercial relationship) is not codified in law.
• Transactional SMS is safer: One-time passwords (OTP), account notifications, delivery alerts, and service updates are de facto acceptable. Marketing SMS, newsletters, and promotional messages should be avoided unless explicit proof of consent exists.
• Sender ID registration: No standardized A2P sender ID registration framework exists. Senders are not required to register a business name, corporate entity, or sender label. Due to sanctions and conflict, international carriers often block SMS claiming to originate from known commercial entities to prevent sanctions evasion.
• Enforcement risk: The regulator has published informal guidance against spam and fraud; however, no transparent enforcement mechanism or published fines are documented. Sender liability is typically civil (contract termination with the operator) rather than criminal.

Critical caveat: US and international sanctions on Houthi-controlled infrastructure create upstream routing constraints independent of Yemen's domestic regulatory framework. Even if your SMS complies with NTC guidance, US-regulated carriers may refuse to route to Houthi-aligned operators. Sender must secure independent legal clearance.

Mobile Operators and Interconnect

Houthi-aligned operators (Yemen Mobile) — 55% market share: Yemen Mobile is the dominant operator in Houthi-controlled territory (North Yemen). International SMS routing to this operator is the most sensitive due to US and international sanctions. Routing partners are limited; delivery success is lowest among the three operators (~75–78%). Sender must have explicit legal authorization.

Saba Telecom — 30% market share: Saba operates in the South and East (internationally recognized government areas). Routing is more stable than Yemen Mobile; international partnerships are more robust. Delivery success is higher (~85–88%). Sender verification may be requested by Saba, though formal A2P registration is not standardized.

Walid Telecom — 15% market share: Walid operates regionally with limited nationwide coverage. International routing is opportunistic; delivery success is variable (~80–84%). Walid has fewer international partnerships and may deprioritize A2P traffic during peak periods.

All three operators are reachable via smsroute.cc's gateway; the platform routes to all available interconnects and reports success/failure per operator in delivery receipts. Latency varies by operator and international routing path (p50: 420 ms; p95: 800 ms). Due to sanctions and conflict, latency may spike during periods of political tension.

How to Send SMS to Yemen in 3 Steps

Step 1: Create a free account
Visit smsroute.cc and sign up with an email address. No phone verification, ID, or corporate documents are required. Your account is active immediately.

Step 2: Top up with crypto
Pay a $5 minimum using Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. No cards, SEPA, or bank transfers. Funds are credited to your account after one blockchain confirmation (typically 2–10 minutes depending on the coin).

Step 3: Send SMS via API or dashboard
Use our REST API or web interface to send messages. Format recipient numbers as E.164 (+967 7XX XXX XXXX). Include required compliance documentation (legal sign-off) for Yemen routing. Delivery reports are returned in real time.

Example: cURL request

Example: Python script

Both examples send a transactional OTP message. The API returns a delivery status immediately; final delivery confirmation is sent to your webhook endpoint once the message reaches the operator.

import requests
import json

api_key = "YOUR_API_KEY"
base_url = "https://api.smsroute.cc"

payload = {
    "to": "+967712345678",
    "text": "Your OTP is 123456",
    "from": "YourApp"
}

headers = {
    "Authorization": f"Bearer {api_key}",
    "Content-Type": "application/json"
}

response = requests.post(f"{base_url}/send", json=payload, headers=headers)
print(json.dumps(response.json(), indent=2))

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+967712345678",
    "text": "Your OTP is 123456",
    "from": "YourApp"
  }'

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/sms/send", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9675551234567",
    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":   "+9675551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/v1/sms/send",
        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'   => '+9675551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/v1/sms/send');
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);