Send SMS to Nigeria
from $0.0110/msg

smsroute delivers SMS to Nigerian mobiles from $0.011 per message — NCC-compliant routes, DND-aware by default. Every promotional send is pre-checked against the NCC 2442 Do Not Disturb registry, every route adapts around the 19:00-22:00 WAT evening congestion peak, and all four operators (MTN, Airtel, Glo, 9mobile) are reached via direct interconnects. Pay in Bitcoin, USDT, Ether, Litecoin, Monero, or Solana. No KYC at signup. 79% cheaper than Twilio on +234 traffic.

The NCC 2442 DND Registry — And Why Your Nigerian SMS Might Be Getting Silently Dropped

If your Nigerian delivery reports show "submitted" but recipients never received the message, the culprit is usually not sender reputation, the gateway, or the handset — it is the 2442 registry.

The Nigerian Communications Commission (NCC) launched the 2442 Do Not Disturb shortcode in 2016 as a free, universal opt-out for every mobile subscriber. A 2018 harmonization directive forced all four operators — MTN, Airtel, Globacom, 9mobile — to honor 2442 with a standardized 3-tier opt-out schema. When a subscriber texts STOP to 2442, their MSISDN enters the operator-side blocklist; from that moment marketing SMS is dropped at the SMSC, not bounced. The sender sees a normal "submitted" receipt. The handset never rings.

Three opt-out tiers:

• Full block (STOP or 0) — all promotional A2P SMS dropped; transactional (OTP, payment, delivery) still delivers.
• Promotional-only block (codes 1-6) — category opt-out: banking/finance, lifestyle, education, religious, health, general promotions. A finance-tagged campaign is dropped to a tier-1 subscriber; a health-tagged one still reaches them.
• Partial block (code 7) — whitelist-only mode. Covers ~8-11% of DND-registered numbers.

The NCC expects automated senders to scrub the registry before every marketing send. Enforcement is operator-side via real-time DND flags on the A2P interconnect — the Commission does not publish a scrub API, and providers that route around operator enforcement via gray routes have drawn action.

smsroute's approach: the traffic_class parameter on every send is either transactional or promotional. Promotional sends are routed through DND-aware interconnects that consult the operator's real-time flag; if the recipient is DND-blocked, we return the dnd_blocked error code and do not charge for the message. Transactional traffic bypasses the DND check, as the regulation permits.

Operator Peak-Hour Routing — The 19:00-22:00 WAT Congestion Problem

Nigeria has a sharply bimodal SMS-traffic profile. P2P volume is low during work hours, then surges in the evening when subscribers return home, eat, and socialize. A2P traffic is the victim.

MTN Nigeria is worst-affected: its SMSC deprioritizes A2P queues during 19:00-22:00 WAT (UTC+1) to preserve P2P latency for 90M+ subscribers. On naive routes MTN A2P p95 rises from ~480ms to 1.2-1.8 seconds. Promotional messages sometimes queue for 30+ seconds.

Airtel Nigeria applies a similar but gentler throttle and has a lower A2P TPS cap overall; evening p95 sits at 800-1100ms. Globacom (Glo) is the most predictable — Mike Adenuga's independent SMSC holds throughput steady, and evening p95 barely moves above daytime. 9mobile inverts the problem: spare peak capacity, but interconnect reliability is lower post-Etisalat, with 0.5-2% transient failures.

smsroute maintains three direct-interconnect paths per operator and continuously rescores them on observed latency. During the 19:00-22:00 window we bias MTN and Airtel traffic toward less-congested paths and raise retry aggressiveness on 9mobile. The measured result over 90 days: Nigeria p95 stays under 820ms even during evening peak, against a fleet p50 of 287ms. For bulk campaigns firing at 18:55 WAT this is the difference between a campaign completing in 12 minutes or 45.

Mobile Operators in Nigeria — Market Dynamics and Operator-Specific Quirks

Nigeria has ~227 million active mobile subscribers against a population of ~220 million — 103% penetration, driven by widespread dual-SIM ownership. Four operators share the market.

Mobile Number Portability has been live since 2013 but adoption is modest — ~1.1% of the base has ever ported. The leading digits are no longer a fully reliable operator indicator, so smsroute does an HLR lookup on first send and caches the operator-of-record for 30 days.

NCC Sender-ID Registration — The $30-50 Process That's Worth It

If you plan to send more than occasional one-off SMS to Nigeria, register your alphanumeric sender ID with the NCC. It is the single highest-ROI compliance step for Nigerian routes.

What it is. An 11-character alphanumeric string (Latin alphabet, no spaces, no emojis) that appears as the "From" on the recipient's handset — e.g. Kuda, Flutterwave, smsroute. Without registration, operators increasingly rewrite unregistered alphanumeric senders to a shared numeric long code, and recipients see a random 10-digit number instead of your brand — depressing open rates by 30-60% depending on category.

The process. smsroute submits the application via our operator partners. The NCC requires the proposed sender ID string, a brief use-case description, and sometimes proof of corporate registration (CAC) for brand-matching senders. One-time fee is $30-50 depending on operator count; turnaround 3-5 business days, occasionally up to 10 during backlog.

The constraints. 11 Latin chars is a hard cap — no extended characters, no emoji, no spaces. Mixed case is fine. Sender IDs impersonating regulated entities (bank names you don't own, NCC itself, NIN/NIMC) are refused, as are case-insensitive duplicates of existing registrations.

How to send SMS to Nigeria in 3 steps

Step 1 — Sign up and register your sender ID

Create an smsroute account at smsroute.cc with email only. From the dashboard, submit your 11-character alphanumeric sender ID for NCC registration. Expect 3-5 business days. While you wait, your transactional OTP sends will still go out — they just will not carry your brand.

Step 2 — Top up with crypto, set traffic class

Minimum $5. USDT TRC-20 credits in roughly 60 seconds. When you call the API, set traffic_class to transactional for OTP / account alerts / delivery notifications, or promotional for marketing. The latter triggers the 2442 DND pre-check; the former bypasses it by regulation.

Step 3 — Send to a +234 number

Format the recipient as +234 followed by the 10-digit mobile number (drop the leading zero if present). The operator prefix after +234 tells you the carrier: 70x, 80x, 81x, 90x, 91x ranges map to MTN/Airtel/Glo/9mobile. smsroute's HLR lookup picks the right operator regardless of portability.

Python — promotional send with explicit DND-awareness:

package main

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

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

import os, requests

r = requests.post(
    "https://api.smsroute.cc/v1/messages",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+2349051234567",
        "from": "Flutterwave",
        "body": "Weekend offer: 0% fees on transfers above NGN 50,000. Opt out: reply STOP.",
        "traffic_class": "promotional",
    },
)
body = r.json()
if body.get("error") == "dnd_blocked":
    print("Recipient is on NCC 2442 DND - no charge, skip retry.")
else:
    print(body["message_id"], body["status"])

curl -X POST https://api.smsroute.cc/v1/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -d '{
    "to": "+2348031234567",
    "from": "smsroute",
    "body": "Your verification code is 471928. Valid 5 minutes.",
    "traffic_class": "transactional"
  }'

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

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

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

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