Send SMS to Georgia
from $0.0160/msg

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

import os, requests

resp = requests.post(
    "https://api.smsroute.cc/v1/sms/send",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+9955551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.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: "+9955551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

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

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

$payload = json_encode([
    'to'   => '+9955551234567',
    '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":   "+9955551234567",
        "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))
}

Consent Framework and Regulatory Compliance

Georgia's primary data protection statute is the Georgian Law on Data Protection, overseen by the regulator GNCC (Georgian National Communications Commission). The GNCC enforces ePrivacy rules that require explicit opt-in consent before any marketing or promotional SMS is sent.

Double opt-in is the safest approach: After a subscriber provides their phone number, send a confirmation SMS or email asking them to confirm they wish to receive messages from your organization. Store proof of consent (timestamp, IP address, subscriber action) in your records. For transactional messages—order confirmations, password resets, two-factor authentication codes, delivery notifications—a soft opt-in may apply (the subscriber has an existing relationship with you and could reasonably expect these messages), but you must still be able to justify and document the commercial context.

Quiet hours must be respected: Do not send marketing SMS outside 09:00–21:00 GET (Georgia Standard Time). No marketing messages on Sundays. Transactional and urgent security messages may override these windows, but marketing campaigns must adhere to the schedule. The GNCC publishes enforcement actions and guidance on its website (https://www.gncc.ge/). Maintain clean contact lists, honour unsubscribe requests immediately, and document your consent collection process. Non-compliance can result in fines in the five- to seven-figure range and suspension from major operators.

Consent Framework and Regulatory Compliance

Georgia's primary data protection statute is the Georgian Law on Data Protection, overseen by the regulator GNCC (Georgian National Communications Commission). The GNCC enforces ePrivacy rules that require explicit opt-in consent before any marketing or promotional SMS is sent.

Double opt-in is the safest approach: After a subscriber provides their phone number, send a confirmation SMS or email asking them to confirm they wish to receive messages from your organization. Store proof of consent (timestamp, IP address, subscriber action) in your records. For transactional messages—order confirmations, password resets, two-factor authentication codes, delivery notifications—a soft opt-in may apply (the subscriber has an existing relationship with you and could reasonably expect these messages), but you must still be able to justify and document the commercial context.

Quiet hours must be respected: Do not send marketing SMS outside 09:00–21:00 GET (Georgia Standard Time). No marketing messages on Sundays. Transactional and urgent security messages may override these windows, but marketing campaigns must adhere to the schedule. The GNCC publishes enforcement actions and guidance on its website (https://www.gncc.ge/). Maintain clean contact lists, honour unsubscribe requests immediately, and document your consent collection process. Non-compliance can result in fines in the five- to seven-figure range and suspension from major operators.

Latency and Delivery Performance

Median latency (p50): 265 milliseconds. Most SMS messages to Georgia are delivered within a quarter-second of transmission. This reflects direct interconnect with Silknet and Caucasus Online.

95th percentile latency (p95): 400 milliseconds. In worst-case scenarios (network congestion, SMS centre queuing), messages may take up to 400 ms. This is still sub-second and acceptable for transactional use.

Delivery success rate: 98.4%. This percentage reflects actual message receipt and does not include bounces from invalid numbers, inactive subscriptions, or handset-level filtering. Maintain a clean contact list—remove undeliverable numbers after 2–3 failed attempts—and your real-world success rate will align closely with smsroute's performance. Transactional messages (order updates, security codes) typically see 99%+ delivery; marketing messages may see 96–98% depending on subscriber engagement and list age.

smsroute maintains 99.9% uptime across its infrastructure. The remaining 0.1% is reserved for planned maintenance windows, which are announced 7 days in advance. We guarantee 99% tier-1 delivery, meaning that if a message fails to deliver, we do not charge you and will attempt a retry. Check your dashboard for real-time delivery reports and per-operator breakdowns.

Related Pages

Related

Related

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

import os, requests

resp = requests.post(
    "https://api.smsroute.cc/v1/sms/send",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+9955551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    },
    timeout=10,
)
resp.raise_for_status()
print(resp.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: "+9955551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

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

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

$payload = json_encode([
    'to'   => '+9955551234567',
    '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":   "+9955551234567",
        "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))
}

Latency and Delivery Performance

Median latency (p50): 265 milliseconds. Most SMS messages to Georgia are delivered within a quarter-second of transmission. This reflects direct interconnect with Silknet and Caucasus Online.

95th percentile latency (p95): 400 milliseconds. In worst-case scenarios (network congestion, SMS centre queuing), messages may take up to 400 ms. This is still sub-second and acceptable for transactional use.

Delivery success rate: 98.4%. This percentage reflects actual message receipt and does not include bounces from invalid numbers, inactive subscriptions, or handset-level filtering. Maintain a clean contact list—remove undeliverable numbers after 2–3 failed attempts—and your real-world success rate will align closely with smsroute's performance. Transactional messages (order updates, security codes) typically see 99%+ delivery; marketing messages may see 96–98% depending on subscriber engagement and list age.

smsroute maintains 99.9% uptime across its infrastructure. The remaining 0.1% is reserved for planned maintenance windows, which are announced 7 days in advance. We guarantee 99% tier-1 delivery, meaning that if a message fails to deliver, we do not charge you and will attempt a retry. Check your dashboard for real-time delivery reports and per-operator breakdowns.

Frequently Asked Questions

Frequently Asked Questions

Related Pages

Related

Related

Related

Related