Send SMS to Guatemala
from $0.0240/msg

Reach 20 million subscribers across Guatemala's four major operators (Claro, Movistar, Tigo, Avantel) with 97.8% delivery at $0.0240 USD per SMS—a 40% savings versus Twilio. smsroute.cc connects directly to each operator, delivering 245 ms median latency and 99.9% uptime. Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. no identity submission, no phone linking, no business docs at signup. $5 minimum top-up. Comply with Guatemala's Ley de Protección de Datos Personales (LPDP) by obtaining express opt-in consent, respecting quiet hours (08:00–20:00 CST for marketing), and registering your sender ID. Start sending today.

The LPDP Rule Every Guatemala Marketing Sender Gets Wrong

Guatemala's Ley de Protección de Datos Personales (LPDP) mandates express opt-in consent before any marketing or promotional SMS is sent. Many senders in the region assume "soft opt-in" — the ability to send one message and let the recipient reply "STOP" to opt out — applies to SMS marketing. It does not. In Guatemala, you must collect documented consent before the first message arrives. This consent must be recorded and retained for inspection by the SIT (Superintendencia de Telecomunicaciones de Guatemala) or other data protection authorities.

The second gotcha: marketing SMS must respect quiet hours between 20:00 and 08:00 CST. Many senders schedule campaigns during off-peak hours expecting higher engagement, only to see messages rejected or delayed by operators enforcing the quiet-hours rule. Transactional SMS (confirmations, alerts, password resets) do not trigger quiet-hours restrictions, but the line between "transactional" and "marketing" must be drawn correctly. If there is any promotional element, tag it as marketing and apply the full LPDP regime: prior consent, quiet hours, opt-out mechanism.

The third gotcha: sender ID registration. While alphanumeric sender IDs (up to 11 characters, Latin only, no spaces) are permitted, different operators apply registration enforcement inconsistently. Claro and Movistar may enforce it strictly; Tigo and Avantel may be more lenient. If your sender ID is not registered with an operator, the message may be relayed as a generic system number or rejected outright. smsroute.cc handles sender ID validation with each carrier to maximize delivery, but you must provide a legitimate, recognizable sender ID that your recipients trust.

Mobile Operators and Market Coverage

Claro Guatemala (45% market share): Claro is the dominant carrier, serving approximately 9 million subscribers. It operates nationwide 4G/LTE coverage and maintains the largest backhaul capacity. Claro enforces sender ID registration for marketing SMS and maintains a relatively strict anti-spam filtering policy. smsroute.cc maintains direct IP-based peering with Claro's SMS gateway, ensuring priority handling and reliable routing. Messages to Claro numbers typically clear with 200–300 ms latency.

Movistar Guatemala (32% market share): Movistar, operated by Telefónica, serves roughly 6.4 million subscribers and is the second-largest operator. Movistar's network coverage is nearly as extensive as Claro's, with good 4G penetration in urban and suburban areas. Movistar also requires sender ID documentation and enforces quiet hours. Direct peering with smsroute.cc ensures consistent delivery and sub-250 ms latency for most messages. Movistar's pricing to end users is competitive, which makes it popular for prepaid segments.

Tigo Guatemala (18% market share): Tigo operates approximately 3.6 million subscribers, with strong presence in provincial markets. Tigo's sender ID enforcement is less strict than Claro or Movistar, though best practice is still to register. smsroute.cc's connection to Tigo offers consistent 250–350 ms latency and equivalent delivery success. Tigo is increasingly attractive for cost-conscious senders in Guatemala, as it has a lower per-SMS cost to route than some competitors.

Avantel (5% market share): Avantel is a smaller, regional carrier serving roughly 1 million subscribers, mainly in specific geographic zones. Despite its smaller footprint, Avantel is operationally robust and profitable. smsroute.cc includes Avantel in its Guatemala routing matrix; messages to Avantel numbers route reliably with latency similar to larger carriers. Avantel also enforces basic compliance rules but may have slightly less sophisticated spam-filtering technology than Claro or Movistar.

All four operators interconnect directly with smsroute.cc's SMS hub, so you send one API request and the message is routed automatically to the correct carrier. There is no need to register with each operator separately (though registering a sender ID with SIT or directly with operators is recommended for marketing campaigns). smsroute.cc's multi-operator routing ensures 97.8% delivery success and redundancy if any single carrier experiences temporary congestion.

Guatemala's Consent Framework: LPDP and SIT Regulation

The Ley de Protección de Datos Personales (LPDP) is Guatemala's primary data protection statute. It applies to any organization collecting, storing, or processing personal data—including phone numbers used for marketing SMS. The law requires:

• Express prior consent: Marketing SMS must not be sent without documented opt-in. The recipient must affirmatively agree in writing, electronically, or verbally (with a recorded confirmation) before the first promotional message.
• Clear purpose statement: Consent must be tied to a specific purpose (e.g., "promotional updates from Company X about products Y and Z"). Blanket, vague consent is insufficient.
• Retention: Consent records must be retained for the duration of the marketing relationship, plus a reasonable period thereafter (typically 2–3 years).
• Right to opt out: Every marketing SMS must include a mechanism for the recipient to withdraw consent (e.g., "Reply STOP to unsubscribe" or a link).

The SIT (Superintendencia de Telecomunicaciones de Guatemala) enforces telecom-specific rules, including sender ID registration, network quality, and spam prevention. While the SIT does not directly enforce LPDP consent (that falls to the data protection authority), the SIT can sanction operators for allowing non-compliant SMS to transit their networks. The regulator publishes enforcement actions and guidance at https://www.sit.gob.gt/. Senders who fail to comply may face administrative fines, temporary service suspension, or reputational damage. Marketing SMS sent between 20:00 CST and 08:00 CST are categorically non-compliant; operators may block them automatically, and the SIT may investigate the sender organization.

Transactional SMS (account confirmations, two-factor authentication, order status, delivery notifications) are not subject to quiet-hours restrictions and do not require prior LPDP consent if the recipient has an existing business relationship with the sender (e.g., they signed up for an account or made a purchase). However, any transactional message that includes promotional content must comply with marketing rules. For example, a password-reset email can include a transactional code, but a password reset SMS that says "Reset your password and check out our 50% off sale!" crosses into marketing territory and requires consent and quiet-hours compliance.

How to Send SMS to Guatemala in Three Steps

Step 1: Create a free account and verify your email. Go to smsroute.cc, fill in your email address, and click "Sign Up." No phone number, ID, or corporate paperwork is required. You will receive a confirmation email within seconds; click the link to activate your account. Your dashboard is now live.

Step 2: Top up your account with cryptocurrency. Navigate to Billing and choose your payment method: Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5. Send the exact amount to the on-screen wallet address. Once the blockchain confirms your transaction (typically within 1–3 minutes), your account balance updates and you are ready to send.

Step 3: Send your first SMS to a Guatemala number. Use the dashboard SMS composer or integrate the API. Phone numbers must be in E.164 format: +502 followed by the 8-digit mobile number. Example: +50272345678 (Claro), +50223456789 (Movistar). Include a sender ID (alphanumeric, up to 11 characters) and ensure the recipient has consented if your message is marketing. Hit Send, and check the delivery report within 2–10 seconds.

cURL Example

Python Example

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

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

import requests

api_key = "YOUR_API_KEY"
url = "https://smsroute.cc/api/sms/send"
headers = {
    "Authorization": f"Bearer {api_key}",
    "Content-Type": "application/json"
}
payload = {
    "to": "+50272345678",
    "message": "Your order #12345 has been shipped. Track it here: [link]",
    "sender_id": "YourStore"
}

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

curl -X POST https://smsroute.cc/api/sms/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+50272345678",
    "message": "Your OTP is 123456. Valid for 10 minutes.",
    "sender_id": "CompanyName"
  }'

package main

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

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