· By smsroute editorial · 8 min read

smsroute delivers SMS to French mobile handsets for $0.022 per message with a Bloctel-compatible, CNIL-safe workflow. Routes cover Orange France (37%), SFR (27%), Bouygues Telecom (19%), and Free Mobile (17%). Median delivery from our Frankfurt POP is 148 ms, 99.3% success rate, $5 crypto minimum top-up, no KYC at signup. Integrate with Opposetel's Bloctel API upstream for scrub-before-send, then fire the message through smsroute.

Bloctel — France's opt-out registry that every SMS sender must check

Bloctel is the legally mandated French opt-out registry for commercial telephone prospecting, created by the Loi Hamon of 2014 (Loi n° 2014-344) and operated on behalf of the DGCCRF by Opposetel SAS. French residents register their mobile and landline numbers voluntarily; once listed, they are withdrawn from the universe of legally addressable cold-prospecting targets. As of early 2026 the registry contains roughly 5.4 million unique numbers, a figure that has grown every quarter since the 2020 decree tightened the enforcement regime.

The statute that governs the scrub obligation is Article L. 223-1 of the Code de la consommation. It obliges any professional who engages in telephonic prospecting toward a natural person to check their list against Bloctel monthly, before each campaign. A scrub older than 30 days is not legally defensible: DGCCRF inspectors are explicitly directed to ask for the scrub timestamp and compare it against the send log. The penalty for sending to a Bloctel-listed number is an administrative fine up to EUR 75,000 per natural person and up to EUR 375,000 per legal person, with repeat violations attracting doubled caps under the 2020 decree.

CNIL enforcement history on commercial-prospection cases is substantial. In October 2023 the CNIL issued a EUR 600,000 sanction against Groupe CANAL+ for consent failings and data-rights violations in its prospection workflow, including SMS campaigns with inadequate consent evidence. In November 2022 the CNIL fined TotalEnergies Électricité et Gaz France EUR 1,000,000 for prospection-related issues including the failure to honor opt-out requests. A series of smaller penalties in the EUR 50,000—500,000 range have landed against data brokers and lead generators whose SMS lists were assembled without a valid legal basis. The DGCCRF runs a parallel administrative-fine track under Article L242-16 Code de la consommation, with sanctions up to EUR 375,000 per legal person for Bloctel violations.

Mechanics of scrubbing: you do not query Bloctel with individual numbers. You upload your prospecting list through an accredited tiers de confiance (currently Opposetel itself and a handful of DGCCRF-approved aggregators), which returns a stripped list with Bloctel-registered numbers removed. The scrub response includes a signed timestamp that serves as your legal proof. Keep scrub receipts for three years. smsroute does not perform the scrub — that is deliberately outside our scope because Bloctel access requires registration with the DGCCRF as an opérateur de démarchage. The pattern we recommend to developers is: CRM — Bloctel scrub via Opposetel API — scrubbed list — smsroute send.

Exemptions are narrow. Transactional SMS (OTP, order confirmations, delivery notifications, alerts) is explicitly outside Article L. 223-1 and does not need scrubbing. B2B prospecting to a recipient reached in their professional capacity (business number, business email corroboration) is out of scope. Contacts collected under an existing commercial relationship where the purchaser was informed at collection that their number could be used for prospection of similar products are covered by the soft opt-in described below, not by Bloctel.

How to send SMS to France in 3 steps

Step 1 — Create an smsroute account

Sign up at smsroute.cc. No phone verification, no ID. If you will do B2C prospection, set up your Bloctel scrub pipeline with Opposetel in parallel.

Step 2 — Top up with crypto

Minimum $5. USDT TRC-20 preferred (sub-$1 fees, ~1 minute confirmation). Bitcoin, Ethereum, Litecoin, Monero, and Solana also accepted. No cards, no SEPA.

Step 3 — Send to +33 6 or 7

French accents (é, è, à, ç) trigger UCS-2 encoding and drop the per-segment character limit from 160 to 70. Budget 2 segments for a typical French-language prospection body.

Mobile operators in France

France has a four-operator market, stable since Free Mobile's disruptive launch in 2012. No operator-consolidation deals are in progress as of 2026.

Orange France. ~37% revenue share, the incumbent national operator, majority state-indirect via Bpifrance. Runs the largest 5G and fibre networks. Our lowest-latency route interconnects directly with Orange at the Paris peering point — 140 ms median.

SFR. ~27% share, owned by Altice France (Patrick Drahi). The company carries a high debt load from the Altice acquisition, which surfaces occasionally in network-investment delays. Interconnect via carrier-of-carriers link — 151 ms median.

Bouygues Telecom. ~19% share, part of the Bouygues SA conglomerate. Announced a network-sharing deal with SFR in 2024 for rural 5G. Interconnect — 149 ms median.

Free Mobile. ~17% share, the Iliad SA challenger launched in 2012 that forced the other three carriers to drop prices. Operates its own FTTH network in parallel to the mobile business. Free tends to be the aggressive edge-pricing operator. Interconnect via Iliad peering — 158 ms median.

Pricing vs competitors

Provider Price per SMS (USD) vs. smsroute
smsroute $0.0220 best price
Twilio$0.0355baseline
Sinch$0.034837% more
Infobip$0.033033% more
Plivo$0.029124% more

Prices as of April 2026, sourced from each provider's public pricing page. smsroute's $0.022 is 40% below Twilio's $0.067. The discount is structural: we route directly to Orange, SFR, Bouygues, and Free Mobile without an additional aggregator hop, and we operate on crypto-only payment rails that eliminate 3-5% card-processor fees.

Latency + delivery success rate

OperatorMarket shareP50 latencyP95 latencyDelivery success
Orange France37%140 ms305 ms99.5%
SFR27%151 ms340 ms99.2%
Bouygues Telecom19%149 ms332 ms99.3%
Free Mobile17%158 ms358 ms99.1%
Blended France100%148 ms330 ms99.3%

Rolling 90-day delivery success rate: 99.3% blended. The 0.7% failure pool splits roughly as 50% handset-off > 48h, 25% ported-number routing glitches (historically worst on Free Mobile), 15% sender-ID rewrite to long code, 10% residual.

CNIL prospection commerciale — what counts as soft opt-in

The CNIL's prospection commerciale guidance, last updated in February 2022, distinguishes B2C from B2B rules and defines a narrow soft opt-in for existing customers. It sits under Article 21 of the Loi Informatique et Libertés (LIL) as transposed from the ePrivacy Directive Art. 13.

B2C cold prospection. Explicit prior consent required, full stop. The consent must be specific, informed, unambiguous, and freely given (Art. 4(11) GDPR). Bundled consents, pre-ticked boxes, and consent collected at service signup that blankets "marketing from us and our partners" all fail. This is the hardest path — only useful if you have your own first-party consent collection.

B2C soft opt-in (existing customer exemption). If you collected the phone number during the sale of a product or service, you may send prospection SMS for similar products from the same brand, provided three conditions are met: (1) at collection, the recipient was clearly told the number would be used for this purpose; (2) every subsequent SMS includes an opt-out mechanism (STOP to 36XXX short code); (3) the products advertised are materially similar to the original purchase. The CNIL has explicitly rejected attempts to stretch "similar" across corporate-group brands or materially different product lines.

B2B prospection. Prior consent is not required where the recipient is reached in their professional capacity, on a professional number, and the communication relates to their professional role. The recipient must still have a simple opt-out available. A message to jean.dupont@entreprise.fr or a corporate mobile qualifies; a message to jean.dupont@gmail.com sourced from a B2B enrichment vendor does not.

Sender ID rules + Bloctel integration pattern

French operators accept alphanumeric sender IDs up to 11 characters, Latin alphabet, no spaces. There is no formal ARCEP pre-registration requirement for commercial senders, but Orange and SFR run spam-filter heuristics that rewrite unregistered alphanumerics to a generic long code on suspicious A2P traffic. Register your sender ID with smsroute in advance to keep the branded ID intact.

The recommended integration pattern for French B2C prospection is a scrub-before-send pipeline that queries Opposetel's Bloctel API before each campaign and only fires smsroute sends against the scrubbed list.

Frequently asked questions

What is Bloctel and when do I have to check it before sending SMS to France?

Bloctel is France's national opt-out registry for telephone prospecting, operated under Article L. 223-1 of the Code de la consommation. Every commercial sender addressing French residents must scrub their list against Bloctel before a cold B2C prospecting campaign. The check must be done in the month preceding the send — the registry refreshes continuously, so a scrub older than 30 days is not legally defensible. Exemptions: transactional SMS (OTPs, alerts, delivery notifications), contacts collected under an existing commercial relationship with explicit consent to be contacted, and B2B communications where the recipient is reached in their professional capacity.

Is OTP/transactional SMS exempt from Bloctel and CNIL consent rules?

Yes. The CNIL's 2022 guidance and the Bloctel decree both exclude transactional messages (one-time passwords, two-factor codes, delivery notifications, appointment reminders, service alerts, password resets) from the opt-out registry and from the prior-consent requirement, on the basis that these communications are necessary to fulfill a service the recipient has already requested. The exemption evaporates the moment the SMS body mixes transactional content with promotional content — the CNIL has treated hybrid messages as prospection commerciale in all published enforcement decisions since 2021.

What are CNIL fines for unconsented SMS prospecting?

The CNIL can impose administrative fines under Article 83 of the GDPR (up to 4% of global annual turnover or EUR 20 million) plus specific French sanctions under Article 20 of the Loi Informatique et Libertés. Recent published enforcement on commercial prospection includes the EUR 600,000 sanction against Groupe CANAL+ (October 2023) for consent failings and data-rights violations, the EUR 1,000,000 sanction against TotalEnergies Électricité et Gaz France (November 2022) for prospection-related issues, and a range of EUR 50,000-500,000 penalties against smaller data brokers and lead generators. Bloctel violations are separately sanctioned by the DGCCRF with administrative fines up to EUR 375,000 per legal person under Article L242-16 Code de la consommation.

How does the soft opt-in exemption work under CNIL guidance?

The CNIL recognises a narrow soft opt-in exemption aligned with Art. 21 of the Loi Informatique et Libertés: if you collected the phone number during the sale of a product or service, you may send SMS prospection for similar products from the same brand, provided (1) the recipient was clearly informed at collection that the number would be used this way, (2) each SMS includes an opt-out mechanism (STOP keyword to a French short code), and (3) the products being advertised are similar in nature to the one originally purchased. The exemption does not apply to data purchased from third parties, to affiliated brands inside a corporate group, or to products materially different from the original purchase.

How do I integrate Opposetel's Bloctel API before calling smsroute's send endpoint?

The compliant pattern is a two-step pipeline: scrub first, send second. Your backend calls Opposetel's Bloctel scrub API with the batch of French numbers you intend to prospect; Opposetel returns the survivor list (numbers not on Bloctel) plus a signed receipt_id and timestamp you retain for three years as your Article L. 223-1 audit trail. You then iterate the survivors into smsroute's send endpoint. Python pattern: requests.post('https://api.opposetel.fr/v2/scrub', json={'numbers': [...]} ) returns {'survivors': [...], 'receipt_id': ...}; persist the receipt to a JSONL audit file; then loop survivors into requests.post('https://api.smsroute.cc/v1/messages', json={'to': n, 'from': 'AcmeShop', 'body': '...'}). Curl equivalent: POST /v2/scrub to Opposetel first, then POST /v1/messages to smsroute per survivor. Bloctel access is restricted to DGCCRF-registered opérateurs de démarchage — the Opposetel account you need sits under that registration. smsroute does not scrub; the scrub is deliberately upstream because the lawful basis and audit trail belong in your own stack.

Is alphanumeric sender ID supported in France?

Yes. Up to 11 characters, Latin alphabet, no spaces. There is no formal ARCEP pre-registration for alphanumeric sender IDs, but Orange and SFR increasingly rewrite unregistered alphanumeric IDs on A2P traffic to a generic French long code. Register your sender ID with smsroute in advance to prevent rewrite. Keep in mind that when you use an alphanumeric sender the SMS is one-way — replies are not routed back unless you provision a dedicated French long code.

Does smsroute scrub against Bloctel automatically before sending?

No. smsroute is a transit provider, not a data processor of your CRM. Bloctel access is restricted to companies registered with the DGCCRF as opérateurs de démarchage, and your list-scrubbing must happen before the API call — the check is done against your own contact database, not against the SMS payload. We log the send events and deliver the messages; the lawful-basis verification is yours. For developers who need a compliant pipeline, we recommend integrating Opposetel's Bloctel API (the DGCCRF-authorised scrubbing gateway) upstream of your smsroute send call.

Related pages

Related

Related

Related

Features SMS API Pricing API Docs Blog
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: "+335551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());
import requests, os

r = requests.post(
    "https://api.smsroute.cc/v1/messages",
    headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
    json={
        "to": "+33612345678",
        "from": "AcmeShop",
        "body": "Votre code de verification: 384921. Valable 10 min. STOP au 36200 pour ne plus recevoir."
    }
)
print(r.json())
curl -X POST https://api.smsroute.cc/v1/messages \
  -H "Authorization: Bearer $SMSROUTE_API_KEY" \
  -d '{
    "to": "+33612345678",
    "from": "AcmeShop",
    "body": "Votre code de verification: 384921. Valable 10 min. STOP au 36200 pour ne plus recevoir."
  }'
package main

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

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

France has a four-operator market, stable since Free Mobile's disruptive launch in 2012. No operator-consolidation deals are in progress as of 2026.

Orange France. ~37% revenue share, the incumbent national operator, majority state-indirect via Bpifrance. Runs the largest 5G and fibre networks. Our lowest-latency route interconnects directly with Orange at the Paris peering point — 140 ms median.

SFR. ~27% share, owned by Altice France (Patrick Drahi). The company carries a high debt load from the Altice acquisition, which surfaces occasionally in network-investment delays. Interconnect via carrier-of-carriers link — 151 ms median.

Bouygues Telecom. ~19% share, part of the Bouygues SA conglomerate. Announced a network-sharing deal with SFR in 2024 for rural 5G. Interconnect — 149 ms median.

Free Mobile. ~17% share, the Iliad SA challenger launched in 2012 that forced the other three carriers to drop prices. Operates its own FTTH network in parallel to the mobile business. Free tends to be the aggressive edge-pricing operator. Interconnect via Iliad peering — 158 ms median.

Pricing vs competitors

Provider Price per SMS (USD) vs. smsroute
smsroute $0.0220 best price
Twilio$0.0355baseline
Sinch$0.034837% more
Infobip$0.033033% more
Plivo$0.029124% more

Prices as of April 2026, sourced from each provider's public pricing page. smsroute's $0.022 is 40% below Twilio's $0.067. The discount is structural: we route directly to Orange, SFR, Bouygues, and Free Mobile without an additional aggregator hop, and we operate on crypto-only payment rails that eliminate 3-5% card-processor fees.

Latency + delivery success rate

OperatorMarket shareP50 latencyP95 latencyDelivery success
Orange France37%140 ms305 ms99.5%
SFR27%151 ms340 ms99.2%
Bouygues Telecom19%149 ms332 ms99.3%
Free Mobile17%158 ms358 ms99.1%
Blended France100%148 ms330 ms99.3%

Rolling 90-day delivery success rate: 99.3% blended. The 0.7% failure pool splits roughly as 50% handset-off > 48h, 25% ported-number routing glitches (historically worst on Free Mobile), 15% sender-ID rewrite to long code, 10% residual.

CNIL prospection commerciale — what counts as soft opt-in

The CNIL's prospection commerciale guidance, last updated in February 2022, distinguishes B2C from B2B rules and defines a narrow soft opt-in for existing customers. It sits under Article 21 of the Loi Informatique et Libertés (LIL) as transposed from the ePrivacy Directive Art. 13.

B2C cold prospection. Explicit prior consent required, full stop. The consent must be specific, informed, unambiguous, and freely given (Art. 4(11) GDPR). Bundled consents, pre-ticked boxes, and consent collected at service signup that blankets "marketing from us and our partners" all fail. This is the hardest path — only useful if you have your own first-party consent collection.

B2C soft opt-in (existing customer exemption). If you collected the phone number during the sale of a product or service, you may send prospection SMS for similar products from the same brand, provided three conditions are met: (1) at collection, the recipient was clearly told the number would be used for this purpose; (2) every subsequent SMS includes an opt-out mechanism (STOP to 36XXX short code); (3) the products advertised are materially similar to the original purchase. The CNIL has explicitly rejected attempts to stretch "similar" across corporate-group brands or materially different product lines.

B2B prospection. Prior consent is not required where the recipient is reached in their professional capacity, on a professional number, and the communication relates to their professional role. The recipient must still have a simple opt-out available. A message to jean.dupont@entreprise.fr or a corporate mobile qualifies; a message to jean.dupont@gmail.com sourced from a B2B enrichment vendor does not.

Sender ID rules + Bloctel integration pattern

French operators accept alphanumeric sender IDs up to 11 characters, Latin alphabet, no spaces. There is no formal ARCEP pre-registration requirement for commercial senders, but Orange and SFR run spam-filter heuristics that rewrite unregistered alphanumerics to a generic long code on suspicious A2P traffic. Register your sender ID with smsroute in advance to keep the branded ID intact.

The recommended integration pattern for French B2C prospection is a scrub-before-send pipeline that queries Opposetel's Bloctel API before each campaign and only fires smsroute sends against the scrubbed list.

import requests, os, datetime, json

# 1. Scrub your list against Bloctel (via Opposetel API)
scrub_response = requests.post(
    "https://api.opposetel.fr/v2/scrub",
    headers={"Authorization": f"Bearer {os.environ['OPPOSETEL_KEY']}"},
    json={"numbers": ["+33612345678", "+33698765432", "+33712121212"]}
)
scrubbed = scrub_response.json()["survivors"]
scrub_receipt_id = scrub_response.json()["receipt_id"]
scrub_ts = datetime.datetime.utcnow().isoformat()

# 2. Log the scrub receipt for 3-year audit trail (Art. L. 223-1 obligation)
with open("bloctel_scrubs.jsonl", "a") as f:
    f.write(json.dumps({
        "receipt_id": scrub_receipt_id,
        "timestamp_utc": scrub_ts,
        "input_count": 3,
        "survivor_count": len(scrubbed)
    }) + "\n")

# 3. Send through smsroute only to survivors
for number in scrubbed:
    requests.post(
        "https://api.smsroute.cc/v1/messages",
        headers={"Authorization": f"Bearer {os.environ['SMSROUTE_API_KEY']}"},
        json={
            "to": number,
            "from": "AcmeShop",
            "body": "Nouveautes printemps. -20% avec code PRINT20. STOP au 36200."
        }
    )

Frequently asked questions

What is Bloctel and when do I have to check it before sending SMS to France?

Bloctel is France's national opt-out registry for telephone prospecting, operated under Article L. 223-1 of the Code de la consommation. Every commercial sender addressing French residents must scrub their list against Bloctel before a cold B2C prospecting campaign. The check must be done in the month preceding the send — the registry refreshes continuously, so a scrub older than 30 days is not legally defensible. Exemptions: transactional SMS (OTPs, alerts, delivery notifications), contacts collected under an existing commercial relationship with explicit consent to be contacted, and B2B communications where the recipient is reached in their professional capacity.

Is OTP/transactional SMS exempt from Bloctel and CNIL consent rules?

Yes. The CNIL's 2022 guidance and the Bloctel decree both exclude transactional messages (one-time passwords, two-factor codes, delivery notifications, appointment reminders, service alerts, password resets) from the opt-out registry and from the prior-consent requirement, on the basis that these communications are necessary to fulfill a service the recipient has already requested. The exemption evaporates the moment the SMS body mixes transactional content with promotional content — the CNIL has treated hybrid messages as prospection commerciale in all published enforcement decisions since 2021.

What are CNIL fines for unconsented SMS prospecting?

The CNIL can impose administrative fines under Article 83 of the GDPR (up to 4% of global annual turnover or EUR 20 million) plus specific French sanctions under Article 20 of the Loi Informatique et Libertés. Recent published enforcement on commercial prospection includes the EUR 600,000 sanction against Groupe CANAL+ (October 2023) for consent failings and data-rights violations, the EUR 1,000,000 sanction against TotalEnergies Électricité et Gaz France (November 2022) for prospection-related issues, and a range of EUR 50,000-500,000 penalties against smaller data brokers and lead generators. Bloctel violations are separately sanctioned by the DGCCRF with administrative fines up to EUR 375,000 per legal person under Article L242-16 Code de la consommation.

How does the soft opt-in exemption work under CNIL guidance?

The CNIL recognises a narrow soft opt-in exemption aligned with Art. 21 of the Loi Informatique et Libertés: if you collected the phone number during the sale of a product or service, you may send SMS prospection for similar products from the same brand, provided (1) the recipient was clearly informed at collection that the number would be used this way, (2) each SMS includes an opt-out mechanism (STOP keyword to a French short code), and (3) the products being advertised are similar in nature to the one originally purchased. The exemption does not apply to data purchased from third parties, to affiliated brands inside a corporate group, or to products materially different from the original purchase.

How do I integrate Opposetel's Bloctel API before calling smsroute's send endpoint?

The compliant pattern is a two-step pipeline: scrub first, send second. Your backend calls Opposetel's Bloctel scrub API with the batch of French numbers you intend to prospect; Opposetel returns the survivor list (numbers not on Bloctel) plus a signed receipt_id and timestamp you retain for three years as your Article L. 223-1 audit trail. You then iterate the survivors into smsroute's send endpoint. Python pattern: requests.post('https://api.opposetel.fr/v2/scrub', json={'numbers': [...]} ) returns {'survivors': [...], 'receipt_id': ...}; persist the receipt to a JSONL audit file; then loop survivors into requests.post('https://api.smsroute.cc/v1/messages', json={'to': n, 'from': 'AcmeShop', 'body': '...'}). Curl equivalent: POST /v2/scrub to Opposetel first, then POST /v1/messages to smsroute per survivor. Bloctel access is restricted to DGCCRF-registered opérateurs de démarchage — the Opposetel account you need sits under that registration. smsroute does not scrub; the scrub is deliberately upstream because the lawful basis and audit trail belong in your own stack.

Is alphanumeric sender ID supported in France?

Yes. Up to 11 characters, Latin alphabet, no spaces. There is no formal ARCEP pre-registration for alphanumeric sender IDs, but Orange and SFR increasingly rewrite unregistered alphanumeric IDs on A2P traffic to a generic French long code. Register your sender ID with smsroute in advance to prevent rewrite. Keep in mind that when you use an alphanumeric sender the SMS is one-way — replies are not routed back unless you provision a dedicated French long code.

Does smsroute scrub against Bloctel automatically before sending?

No. smsroute is a transit provider, not a data processor of your CRM. Bloctel access is restricted to companies registered with the DGCCRF as opérateurs de démarchage, and your list-scrubbing must happen before the API call — the check is done against your own contact database, not against the SMS payload. We log the send events and deliver the messages; the lawful-basis verification is yours. For developers who need a compliant pipeline, we recommend integrating Opposetel's Bloctel API (the DGCCRF-authorised scrubbing gateway) upstream of your smsroute send call.

Related pages

Related

Related

Related

Related