Send SMS to Bhutan
from $0.0180/msg

import os, requests

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

curl -X POST https://api.smsroute.cc/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+9755551234567",
    "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/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9755551234567",
    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":   "+9755551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

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

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

Latency & Delivery Performance to Bhutan

smsroute maintains 99.9% uptime and operates at 99% tier-1 delivery standards for all routes. To Bhutan specifically:

• Latency p50 (median): 125 milliseconds from API submission to handset receipt.
• Latency p95 (95th percentile): 190 milliseconds. This reflects occasional queuing during peak hours (07:00–09:00 IST) and DIT policy checks.
• Delivery success: 98.0% across B-Mobile and TashiCell. Failures are typically subscriber-side (phone off, barred, out-of-service) or DIT policy blocks (consent missing, quiet-hour violation, rate limit exceeded). All failures return detailed bounce codes; no silent drops.

Our direct SMPP interconnects to both carriers ensure messages bypass international gateways and intermediaries. This direct path is why Bhutan latency is competitive despite geographic isolation. Bhutan's two-operator duopoly also simplifies routing—no multi-carrier arbitrage needed—and our prefix tables are updated weekly to reflect any carrier splits or number plan changes published by DIT.

Latency & Delivery Performance to Bhutan

smsroute maintains 99.9% uptime and operates at 99% tier-1 delivery standards for all routes. To Bhutan specifically:

• Latency p50 (median): 125 milliseconds from API submission to handset receipt.
• Latency p95 (95th percentile): 190 milliseconds. This reflects occasional queuing during peak hours (07:00–09:00 IST) and DIT policy checks.
• Delivery success: 98.0% across B-Mobile and TashiCell. Failures are typically subscriber-side (phone off, barred, out-of-service) or DIT policy blocks (consent missing, quiet-hour violation, rate limit exceeded). All failures return detailed bounce codes; no silent drops.

Our direct SMPP interconnects to both carriers ensure messages bypass international gateways and intermediaries. This direct path is why Bhutan latency is competitive despite geographic isolation. Bhutan's two-operator duopoly also simplifies routing—no multi-carrier arbitrage needed—and our prefix tables are updated weekly to reflect any carrier splits or number plan changes published by DIT.

Bhutan's Consent Framework: Personal Data Protection Act (2021)

Bhutan's Personal Data Protection Act (2021) governs all SMS marketing and customer communication. The regulator, the Department of Information Technology (DIT), enforces marketing consent rules strictly. Unlike some jurisdictions that permit soft opt-in (pre-existing business relationship without explicit consent), Bhutan requires documented, explicit written consent before any marketing SMS is sent.

Senders must obtain affirmative consent from each recipient—a signed form, email confirmation, or in-app opt-in checkbox—and store proof of consent for audit. Consent records should include the date, method, and exact permissions granted (e.g., "SMS for promotional offers"). Recipients must be able to withdraw consent via reply SMS ("STOP"), unsubscribe link, or written request, honored within 48 hours.

The DIT publishes enforcement guidance and has published enforcement actions against carriers and senders for marketing spam and consent violations. Violations carry administrative penalties, though we do not cite specific amounts. Transactional SMS (OTP, password resets, delivery confirmations) do not require explicit marketing consent but must still be accurate and timely.

Marketing SMS must be sent between 08:00 and 21:00 IST (UTC+5:30). Avoid sending during Bhutanese national holidays (National Day, Buddhist festivals such as Tshechu and Paro festival) unless you hold explicit recipient permission to do so. Always include your sender identity (registered alphanumeric ID or company name) and an unsubscribe mechanism in every marketing message.

Related Pages

Explore other countries and resources:

Related

Related

import os, requests

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

curl -X POST https://api.smsroute.cc/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+9755551234567",
    "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/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+9755551234567",
    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":   "+9755551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

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

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

Bhutan's Consent Framework: Personal Data Protection Act (2021)

Bhutan's Personal Data Protection Act (2021) governs all SMS marketing and customer communication. The regulator, the Department of Information Technology (DIT), enforces marketing consent rules strictly. Unlike some jurisdictions that permit soft opt-in (pre-existing business relationship without explicit consent), Bhutan requires documented, explicit written consent before any marketing SMS is sent.

Senders must obtain affirmative consent from each recipient—a signed form, email confirmation, or in-app opt-in checkbox—and store proof of consent for audit. Consent records should include the date, method, and exact permissions granted (e.g., "SMS for promotional offers"). Recipients must be able to withdraw consent via reply SMS ("STOP"), unsubscribe link, or written request, honored within 48 hours.

The DIT publishes enforcement guidance and has published enforcement actions against carriers and senders for marketing spam and consent violations. Violations carry administrative penalties, though we do not cite specific amounts. Transactional SMS (OTP, password resets, delivery confirmations) do not require explicit marketing consent but must still be accurate and timely.

Marketing SMS must be sent between 08:00 and 21:00 IST (UTC+5:30). Avoid sending during Bhutanese national holidays (National Day, Buddhist festivals such as Tshechu and Paro festival) unless you hold explicit recipient permission to do so. Always include your sender identity (registered alphanumeric ID or company name) and an unsubscribe mechanism in every marketing message.

Frequently Asked Questions

Frequently Asked Questions

Related Pages

Explore other countries and resources:

Related

Related

Related

Related