Spain sets a hard registration deadline
An SMS API in Spain now runs into a firm deadline. Under Order TDF/149/2025 (BOE, 2025), Spain's regulator (the CNMC) requires every alphanumeric sender ID (alias) registered in a national database by 15 September 2026. After that date, any SMS, MMS, or RCS to a Spanish number using an unregistered alias is summarily blocked by the operators.
Here's the CNMC registry, the deadline, and how to send Spanish SMS compliantly. SMSRoute's published route page for Spain lists direct-carrier delivery via Movistar, Vodafone, Orange from $0.042/message, with 88ms median submission and 98.7% delivered success (smsroute.cc route pages, 2026).
The CNMC registry
| Requirement | Detail |
|---|---|
| Sender ID (alias) registration | Mandatory in the CNMC national database |
| Legal basis | Order TDF/149/2025 (BOE, 2025) |
| Deadline | 15 September 2026 |
| Unregistered alias | Summarily blocked by operators |
| Applies to | SMS, MMS, and RCS |
| Purpose | Anti-smishing (SMS phishing) protection |
The CNMC alias registry is the core. Every alphanumeric sender ID for Spanish traffic must be verified in the national database. Only the legitimate owner can register a given brand name. The 15 September 2026 deadline is firm. After it, unregistered aliases are blocked outright. And the rule covers SMS, MMS, and RCS alike, so it's channel-wide. On consent, Spain follows the EU GDPR model, mirroring the GDPR-style opt-in discipline across the bloc. For more on the regulatory framework, see the GSMA's anti-smishing guidelines.
One point wort
Sending compliantly in Spain
- Register your alias with the CNMC before the deadlineGet your alphanumeric sender ID verified in the CNMC national database ahead of 15 September 2026. After that, unregistered aliases are blocked.
- Get GDPR consent for marketingSpain follows EU GDPR. Documented opt-in for marketing, honored opt-out. The consent discipline mirrors Germany and the rest of the EU.
- Cover all channelsThe CNMC rule applies to SMS, MMS, and RCS. If you use any of these to Spanish numbers with an alias, register it.
- Plan transactional trafficOTPs and transactional messages need consent-light handling, but if they use a branded alias, that alias must still be registered. The transactional carve-out applies to consent, not the alias registry.
curl -X POST https://api.smsroute.cc/sms/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+34600000000",
"from": "YourBrand",
"message": "Your OTP is 123456"
}'
The deadline is the thing to act on. Unlike markets where unregistered senders are merely relabeled, Spain will block them entirely from 15 September 2026. That means a brand that misses the CNMC registration doesn't just lose its name on messages — it loses delivery. Register the alias well before the deadline. Visit the CNMC’s online registry at sede.cnmc.gob.es. You will need your NIF, a valid digital certificate, and the alias details.
Sending to Spain in practice
SMSRoute is a no-KYC SMS API with crypto billing (BTC, ETH, USDT, XMR, LTC, and SOL) serving the international route to Spain, with live pricing on the send SMS to Spain page. The decisive point for Spain: from 15 September 2026, a CNMC-registered alias is required for any branded sending, or the message is blocked. That registration is a domestic process for the alias you use.
Pair us for transactional delivery with a CNMC-registration path for your branded alias. This is part of a broader European anti-smishing shift (see also the UK's 2026 Ofcom rules and sender-ID registration map).
Related reading
FAQ
Do I need to register my sender ID to send SMS in Spain?
What happens if I don't register my alias in Spain?
Does Spain's CNMC rule apply to RCS and MMS too?
Why is Spain requiring sender ID registration?
Send your first SMS in 5 minutes
No KYC. Pay with BTC, ETH, USDT, XMR, LTC, and SOL. Live routes to 149 countries.
Get an API key →