Send SMS to Afghanistan
from $0.0140/msg

Mobile Operators and Interconnect Quality

Roshan (30% market share): Afghanistan's largest mobile operator by subscriber count, with roughly 11.1 million customers. Roshan's network covers major urban centers and key provincial routes. Direct interconnect with Roshan is via their SMSC in Kabul; latency to Roshan handsets averages 135 ms. Roshan enforces strict content filtering and requires pre-approval of all sender IDs through MCIT.

MTN Afghanistan (28% market share): Second-largest operator with approximately 10.4 million subscribers. MTN's infrastructure spans urban and semi-rural areas. Their SMSC operates in Kabul with average delivery latency of 145 ms. MTN requires the same MCIT registration as Roshan and has comparable content filters for Islamic norm compliance.

AWCC (25% market share): Afghanistan Wireless Communication Company, with roughly 9.3 million subscribers, primarily in central and southern regions. AWCC's SMSC is routed through Kabul; average latency is 150 ms. AWCC is more selective regarding sender approval and often requires written confirmation of opt-in consent practices before activating new sender IDs.

Etisalat Afghanistan (17% market share): The smallest of the four major carriers, with approximately 6.3 million subscribers, concentrated in western and northern Afghanistan. Etisalat's SMSC is accessible via direct peering; latency averages 155 ms. Etisalat enforces the strictest content policies and may require additional documentation for sender approval.

Combined, these four operators serve 37 million subscribers across a population of roughly 40 million (mobile penetration: 78%). smsroute's per-SMS pricing applies equally across all four operators; no premium or discount is applied based on operator selection. Load balancing and failover are automatic—if one operator's SMSC is unavailable, traffic is rerouted to another operator's gateway without duplicate billing.

Pricing vs. Competitors: smsroute Saves 55% vs. Twilio

smsroute's $0.0140 rate is all-inclusive: no setup fees, no monthly minimums, no per-operator surcharges. You are billed only for each SMS successfully sent. By contrast, Twilio ($0.0311) does not charge setup fees but offers no volume discounts for Afghanistan. Vonage, MessageBird, Sinch, and Plivo offer competitive rates but require KYC and bank transfer payments, adding compliance overhead and payment delay. If you send 10,000 SMS to Afghanistan per month, smsroute costs $140 compared to Twilio's $311—a saving of $171 monthly, or $2,052 annually.

Latency and Delivery Performance

smsroute's infrastructure in Afghanistan is optimized for low-latency delivery. The median time from API submission to SMSC acceptance (p50) is 140 milliseconds. The 95th percentile (p95) is 220 milliseconds, meaning that 95% of all SMS to Afghanistan are accepted by the operators within 220 ms. This performance is measured across all four major operators (Roshan, MTN Afghanistan, AWCC, Etisalat) during all hours of operation, including peak traffic periods.

Delivery success rate is 95.8%—a measure of SMS that are accepted by the operators' SMSCs and delivered to valid, active handsets. The remaining 4.2% failure rate is typically attributable to invalid numbers (non-existent mobile prefixes), inactive SIM cards, and carrier-side delivery blocks. Failures are reported in the delivery receipt within seconds of send attempt, allowing you to identify and retry undelivered messages if desired.

Uptime is 99.9%, calculated as monthly availability of the API endpoint. Our infrastructure uses redundant SMSC connections across all four operators; if one connection fails, traffic is automatically rerouted. Tier-1 delivery is guaranteed at 99%, meaning that 99% of all SMS are routed through primary, first-class interconnects rather than backup routes or aggregators.

Islamic Law and Taliban Governance: Consent, Content, and Quiet Hours

Afghanistan's regulatory framework is governed by Islamic Law (Sharia) as interpreted by the Taliban administration (since August 2021) and formalized through government decrees and MCIT guidelines. Unlike Western regulatory bodies, the Afghan framework does not center on privacy legislation alone; it prioritizes alignment with Islamic norms and does not permit marketing of certain product categories, notably financial services, cryptocurrency, and Western secular products. Any sender operating in Afghanistan must ensure that all SMS content—whether transactional or promotional—respects these principles.

Consent requirements are explicitly defined: explicit opt-in consent is mandatory. Recipients must have actively requested SMS or enrolled in a service; soft opt-in (permission implied by prior transaction or web submission) is not recognized. This is a stricter standard than most Western markets. The regulatory enforcement varies in intensity; MCIT has issued enforcement actions against senders for non-compliant content, though specific fines and case names are not publicly documented. Compliance risk is therefore elevated for senders unaccustomed to Islamic norms.

Quiet hours are strictly enforced: marketing SMS must only be sent between 08:00 and 21:00 AFT (UTC+4:30). Outside these hours, only transactional messages (order confirmations, OTP codes, delivery notifications) may be sent. Additionally, all Islamic holidays must be respected—Eid al-Fitr, Eid al-Adha, Ashura, and other major holidays are no-send periods. Mandatory prayer times (Fajr, Dhuhr, Asr, Maghrib, Isha) should also be avoided for non-urgent SMS. smsroute's dashboard includes a compliance calendar with these dates pre-populated.

Registration with MCIT is non-negotiable for any commercial sender. Unregistered sender IDs will be rejected by the operators' SMSCs. The application process requires a description of your intended use case, confirmation of opt-in consent mechanisms, and confirmation of Islamic norm compliance. Due to post-2021 political uncertainty in Afghanistan, enforcement practices and approval timelines remain subject to change. We recommend monitoring MCIT's official announcements and consulting local legal counsel if regulatory risk is a primary concern.

Frequently Asked Questions

Related

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+93701234567",
    "message": "Your message text here",
    "sender_id": "YourCompanyName"
  }'

import requests

API_TOKEN = "YOUR_API_TOKEN"
API_URL = "https://api.smsroute.cc/send"

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

payload = {
    "to": "+93701234567",
    "message": "Your message text here",
    "sender_id": "YourCompanyName"
}

response = requests.post(API_URL, headers=headers, json=payload)
print(response.json())

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: "+935551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

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

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

$payload = json_encode([
    'to'   => '+935551234567',
    '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);

package main

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

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+935551234567",
        "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))
}