Send SMS to Paraguay
from $0.0160/msg

Mobile Operators: Coverage and Interconnect

Claro Paraguay (47% market share) is the largest operator by subscriber count and delivers to both Asunción and regional areas. Mobile numbers are formatted as +595 9 (area code) (6–7 digit local number). Claro interconnect is direct; delivery is reliable and typically immediate.

Tigo Paraguay (30% market share) covers all departments and urban/rural areas nationwide. Tigo numbers also follow the +595 9 (area) (local) format. Tigo has strong regional penetration and is preferred by users in interior departments. Direct interconnect with smsroute.cc; p50 delivery is sub-300 ms in most regions.

Personal Paraguay (23% market share) focuses on prepaid and competitive pricing segments. Personal numbers use the same +595 9 (area) (local) numbering scheme. Personal has slightly higher failure rates on some network conditions, but smsroute.cc's 98.5% overall delivery success factors in any network variance.

All three operators require mobile numbers in E.164 format (+595 9xx xxxxxx or +595 97x xxxxxx) for A2P SMS. smsroute.cc handles format validation and operator routing automatically; you provide the recipient number and message text, and the platform selects the appropriate operator via HLR lookup.

Pricing vs. Competitors

smsroute.cc offers the lowest per-message cost for Paraguay A2P SMS. Below is a side-by-side comparison of leading platforms:

smsroute.cc's $0.0160 rate represents a 42% discount versus Twilio ($0.0276). Over the course of a year, sending 100,000 SMS to Paraguay users would cost $1,600 with smsroute.cc versus $2,760 with Twilio—a savings of $1,160. For cryptocurrency platforms with recurring user verification or transaction alert flows, this difference is material. Additionally, smsroute.cc's crypto-only billing and zero-KYC model eliminate onboarding friction for projects that operate in jurisdictions where traditional payment processors carry compliance overhead.

Delivery Speed and Reliability

Median delivery time (p50): 235 milliseconds. This means half of all SMS sent via smsroute.cc to Paraguay arrive within 235 ms of transmission. 95th percentile (p95): 575 milliseconds. This guarantees that 95% of messages arrive within 575 ms, even during peak network load.

Delivery success rate: 98.5% across Claro Paraguay, Tigo Paraguay, and Personal Paraguay combined. Failed deliveries are typically due to:

• Invalid or disconnected recipient numbers (HLR indicates no active subscription)
• Recipient device out of coverage or powered off (transient; retry available)
• Operator-side temporary congestion (rare; smsroute.cc queues and retries)
• Sender ID or content flagged by operator filter (compliance issue; see Ley 1682 section)

For time-sensitive use cases (OTP delivery, security alerts, transaction confirmations), the sub-300 ms median and 98.5% success rate ensure near-instantaneous user experience. For non-critical promotional messages, you can configure longer timeout windows or implement retry logic. smsroute.cc's webhook delivery receipts provide full visibility into success/failure reasons, enabling you to refine recipient lists and sender ID strategies over time.

Consent Framework: Ley 1682 and CONATEL Compliance

Paraguay's primary privacy and consent regulation is Ley 1682, the Law on Protection of Personal Data (Ley de Protección de Datos Personales), which came into force in 2011 and is enforced by CONATEL (Comisión Nacional de Telecomunicaciones). This statute requires explicit opt-in consent before sending marketing or promotional SMS to any recipient. "Marketing SMS" includes promotions, account upsells, product announcements, and any message not directly tied to a pre-existing transaction, account maintenance, or security event.

Transactional SMS does not require explicit marketing consent. This category includes:

• One-Time Passwords (OTP) for account login or transaction verification
• Password reset or account recovery codes
• Order confirmations or delivery status notifications
• Account security alerts (unauthorized access, login from new device)
• Transaction alerts (deposits, withdrawals, balance notifications)
• Customer support responses to inquiries the user has initiated

For marketing or promotional SMS, you must maintain documented evidence of explicit opt-in consent. This can take the form of checkbox consent in a sign-up flow, confirmation email or SMS, or recorded phone call—provided the recipient can easily demonstrate they agreed to receive marketing messages. CONATEL has published enforcement guidance on this standard. If a recipient does not recognize your sender ID or claims they did not consent, CONATEL may investigate, and the sender may be required to produce consent records or face suspension from operators.

Sender ID registration is recommended but not mandatory. However, CONATEL recommends that high-volume senders (particularly those sending marketing campaigns) register their alphanumeric sender ID with the regulator. This registration strengthens compliance posture and can improve delivery rates, as operators recognize registered IDs. Your SMS must also include a clear opt-out instruction (e.g., "Reply STOP to unsubscribe") for marketing messages.

Frequently Asked Questions

Related

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+595981234567",
    "message": "Your verification code is 123456",
    "sender_id": "MyApp"
  }'

import requests

api_key = "YOUR_API_KEY"
payload = {
    "to": "+595981234567",
    "message": "Your verification code is 123456",
    "sender_id": "MyApp"
}

response = requests.post(
    "https://api.smsroute.cc/send",
    json=payload,
    headers={"Authorization": f"Bearer {api_key}"}
)

print(response.json())

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+5955551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

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

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

$payload = json_encode([
    'to'   => '+5955551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

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

package main

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

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+5955551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/v1/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))
}