Send SMS to Netherlands
from $0.0190/msg

Send SMS to 19.2 million Dutch subscribers via KPN (38%), Vodafone (28%), T-Mobile (25%), and Tele2 (9%) at $0.0190 USD per message. 155 ms median latency, 99.2% delivery success, zero KYC at signup. Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up $5. No monthly fees, no setup costs, no hidden charges.

The GDPR Double Opt-In Rule Every Netherlands Marketing Sender Gets Wrong

The Netherlands enforces GDPR and the Dutch Telemarketing Law (Wtb-2008), which mandate explicit consent before any promotional SMS reaches a Dutch mobile number. Many senders mistakenly believe that a single opt-in is sufficient, or that recipients implicitly consent if they have previously interacted with a brand. This is incorrect. In practice, the Dutch regulator—the Authority for Consumers and Markets (ACM)—requires double opt-in for SMS marketing: first consent to receive promotional messages, then confirmation of that choice. Soft opt-in (the legal framework that permits marketing SMS after a purchase, without re-confirmation) does not apply to SMS in the Netherlands; it is reserved for email under certain narrow conditions. Senders who rely on single consent, purchased lists, or weak affirmative signals risk complaints to the ACM, operator blocks, and reputational damage.

The second critical mistake is sender ID registration. Many platforms allow you to send SMS with an unregistered alphanumeric sender ID—say, "MyCompany"—and assume it will appear on the recipient's phone. In the Netherlands, KPN, Vodafone, T-Mobile, and Tele2 routinely rewrite unregistered sender IDs with generic text or numbers, stripping your branding and reducing trust. Pre-registering your sender ID with the operator ensures your name appears correctly and signals to recipients that the message is legitimate. Failure to register often results in poor engagement and higher complaint rates.

Dutch Consent Framework: GDPR, Wtb-2008, and Operator Enforcement

The Authority for Consumers and Markets (ACM; www.acm.nl) is responsible for enforcing telemarketing rules in the Netherlands. The legal foundation is GDPR Article 21 (direct marketing), combined with the Dutch Telemarketing Law (Wtb-2008, the Telecommunications Consumer Protection Act). Under GDPR, consent for marketing SMS must be explicit, informed, and freely given. Under Wtb-2008, senders must also respect quiet hours and validate that the recipient has affirmatively agreed to receive promotional messages.

Soft opt-in does not exist for SMS in the Netherlands, even if the recipient is an existing customer. Soft opt-in applies only to email marketing in limited circumstances (e.g., transactional follow-ups where the customer's email is already held for fulfillment). For SMS, you must obtain affirmative consent before sending any promotional message, regardless of prior relationship. This consent must be documented and stored; the ACM expects senders to be able to produce proof of consent if challenged.

Quiet hours are enforced as well. Marketing SMS may only be sent between 08:00 and 20:30 CET on weekdays and Saturdays, and not before 10:00 CET on Sundays. Transactional messages (order confirmations, password resets, delivery notifications) are exempt from quiet-hour restrictions but must still comply with the messaging content rules. The ACM publishes enforcement actions against major senders who repeatedly violate these rules; operators may also block sender IDs or numbers that cause high complaint rates.

Mobile Operators and Coverage

KPN Mobile (38% market share) is the largest operator in the Netherlands and operates the most extensive 4G and 5G infrastructure. KPN interconnects directly with smsroute.cc and accepts both alphabetic and numeric sender IDs. Registration is recommended but not mandatory for transactional messages; for marketing, pre-registration is strongly advised. KPN enforces consent rules strictly and publishes a compliance checklist for senders on its B2B portal.

Vodafone Netherlands (28% market share) serves a large customer base in urban and suburban areas. Vodafone's SMS delivery is reliable, with standard latencies of 100–300 ms. Alphanumeric sender ID registration is available via Vodafone's developer portal; unregistered IDs may be rewritten. Vodafone also enforces quiet hours and blocks sender IDs that generate high complaint rates.

T-Mobile Netherlands (25% market share) is the third-largest operator. T-Mobile interconnects with smsroute.cc and supports both alphanumeric and numeric sender IDs. Sender ID pre-registration is optional for transactional messages but mandatory for marketing campaigns. T-Mobile applies similar consent enforcement as KPN and Vodafone; senders must provide evidence of double opt-in if challenged by the regulator.

Tele2 Netherlands (9% market share) is a smaller carrier but maintains direct SMS interconnection. Tele2 also respects GDPR, Wtb-2008, and quiet hours. In total, these four operators cover 19.2 million mobile subscribers (116% penetration, reflecting multi-SIM users and IoT devices). smsroute.cc's direct interconnects with all four ensure near-complete national reach and fast, reliable delivery.

How to Send SMS to the Netherlands in 3 Steps

Step 1: Create a free account. Visit smsroute.cc, sign up with an email address and password. No phone verification, no ID upload, no corporate registration documents required. You receive an API key and API secret immediately, with no waiting period.

Step 2: Top up your account with cryptocurrency. Generate a unique wallet address in your account dashboard and send Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5 USD. Credits appear in your account within one to three blockchain confirmations—typically 15 minutes.

Step 3: Send SMS via the REST API. Make an HTTP POST request to the /api/send endpoint with your API key, target phone number in E.164 format (e.g., +31612345678), an alphanumeric sender ID (11 characters max), and your message body. The API returns a unique message ID and delivery status. Use webhooks or the status endpoint to track delivery in real time. Example requests follow.

cURL example:

Python example:

The API accepts both domestic format (06xxxxxxxx) and E.164 format (+31 6xxxxxxxx); the system normalizes them internally. Sender ID must be alphanumeric, 11 characters or fewer. For marketing campaigns, ensure all recipients have given explicit double opt-in consent and that you are sending only during permitted quiet hours (08:00–20:30 CET, no Sundays before 10:00 CET).

package main

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

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

import os, requests

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

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

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

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