Send SMS to Luxembourg
from $0.0210/msg

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

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

import os, requests

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

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

package main

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

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

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

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

Mobile Operators and Market Coverage

Luxembourg has 0.7 million mobile subscribers with 108% mobile penetration (multiple SIM cards per person are common). The mobile market is dominated by four operators:

Mobile Operators and Market Coverage

Luxembourg has 0.7 million mobile subscribers with 108% mobile penetration (multiple SIM cards per person are common). The mobile market is dominated by four operators:

Luxembourg ePrivacy Law and GDPR Consent Rules

The regulator responsible for SMS compliance in Luxembourg is the Institut Luxembourgeois de Régulation (ILR). Their website is https://www.ilr.public.lu/.

Luxembourg's ePrivacy Law (implemented via the GDPR and national regulations) requires that any organization sending promotional SMS must obtain explicit prior consent from the recipient. This is not a "yes unless they opt out" rule; it is a "no, unless they explicitly opt in and you document it" rule. Key points:

• Explicit opt-in required: A clear, affirmative action by the subscriber (e.g., ticking a checkbox, replying "YES" to a confirmation SMS) must be recorded with timestamp and consent method.
• No soft opt-in: Consent obtained during a purchase, account signup, or registration for an unrelated service does not satisfy the SMS consent requirement.
• Retention obligation: Keep detailed logs of consent for at least three years. Include the date, method (e.g., web form, SMS confirmation), the subscriber's phone number, and the sender ID under which they will receive messages.
• Quiet hours: SMS sends are restricted between 20:00 and 08:00 CET. Weekends are also restricted for unsolicited commercial SMS. Scheduled messages outside quiet hours reduce complaint risk and improve delivery.
• Enforcement: The ILR has published enforcement actions against major senders for insufficient consent documentation. Non-compliance can result in sender ID blocking at POST Telecom, Vodafone, and Orange networks, plus fines in the five- to seven-figure range for enterprises.

Luxembourg ePrivacy Law and GDPR Consent Rules

The regulator responsible for SMS compliance in Luxembourg is the Institut Luxembourgeois de Régulation (ILR). Their website is https://www.ilr.public.lu/.

Luxembourg's ePrivacy Law (implemented via the GDPR and national regulations) requires that any organization sending promotional SMS must obtain explicit prior consent from the recipient. This is not a "yes unless they opt out" rule; it is a "no, unless they explicitly opt in and you document it" rule. Key points:

• Explicit opt-in required: A clear, affirmative action by the subscriber (e.g., ticking a checkbox, replying "YES" to a confirmation SMS) must be recorded with timestamp and consent method.
• No soft opt-in: Consent obtained during a purchase, account signup, or registration for an unrelated service does not satisfy the SMS consent requirement.
• Retention obligation: Keep detailed logs of consent for at least three years. Include the date, method (e.g., web form, SMS confirmation), the subscriber's phone number, and the sender ID under which they will receive messages.
• Quiet hours: SMS sends are restricted between 20:00 and 08:00 CET. Weekends are also restricted for unsolicited commercial SMS. Scheduled messages outside quiet hours reduce complaint risk and improve delivery.
• Enforcement: The ILR has published enforcement actions against major senders for insufficient consent documentation. Non-compliance can result in sender ID blocking at POST Telecom, Vodafone, and Orange networks, plus fines in the five- to seven-figure range for enterprises.

Pricing: smsroute vs. Competitors

smsroute offers the lowest cost-per-message for Luxembourg SMS among major gateways:

smsroute's pricing advantage comes from direct interconnection with POST Telecom, Vodafone, and Orange, and zero overhead from KYC, fraud prevention infrastructure, or regulatory compliance documentation. Crypto-only payment eliminates processing fees and chargeback risk.

Pricing: smsroute vs. Competitors

smsroute offers the lowest cost-per-message for Luxembourg SMS among major gateways:

smsroute's pricing advantage comes from direct interconnection with POST Telecom, Vodafone, and Orange, and zero overhead from KYC, fraud prevention infrastructure, or regulatory compliance documentation. Crypto-only payment eliminates processing fees and chargeback risk.

Latency and Delivery Success

Median latency (p50): 160 milliseconds. This is the time between message submission via API and network acknowledgment from the recipient's operator. 95th percentile latency (p95) is 315 milliseconds. Latency may increase if your sender ID is not pre-registered with POST Telecom, Vodafone, or Orange, because unrecognized IDs are routed through content filtering queues.

Delivery success: 99.0%. Messages are delivered to the recipient's handset or, if the device is offline, queued by the operator for up to 72 hours. Failed messages are returned in the API response with a failure reason code: invalid number format, number not in service, recipient has opted out, content filtering block, etc. You can use these codes to clean your database and retry with corrected numbers or updated consent status.

Delivery success is further improved by:

• Staying within quiet hours (08:00–20:00 CET, weekdays only).
• Pre-registering your sender ID with the operators before launch.
• Including an unsubscribe link in every marketing message.
• Maintaining a clean, consent-documented subscriber list.

Latency and Delivery Success

Median latency (p50): 160 milliseconds. This is the time between message submission via API and network acknowledgment from the recipient's operator. 95th percentile latency (p95) is 315 milliseconds. Latency may increase if your sender ID is not pre-registered with POST Telecom, Vodafone, or Orange, because unrecognized IDs are routed through content filtering queues.

Delivery success: 99.0%. Messages are delivered to the recipient's handset or, if the device is offline, queued by the operator for up to 72 hours. Failed messages are returned in the API response with a failure reason code: invalid number format, number not in service, recipient has opted out, content filtering block, etc. You can use these codes to clean your database and retry with corrected numbers or updated consent status.

Delivery success is further improved by:

• Staying within quiet hours (08:00–20:00 CET, weekdays only).
• Pre-registering your sender ID with the operators before launch.
• Including an unsubscribe link in every marketing message.
• Maintaining a clean, consent-documented subscriber list.

Frequently Asked Questions

Frequently Asked Questions

Related