Sending SMS means meeting carrier and regulator rules: A2P 10DLC registration in the US, opt-out keyword handling everywhere, and sender-ID pre-registration in many countries. Bird runs each from one place and reports status through the API.
Compliance is the layer of the Bird SMS API that keeps your traffic deliverable. Different regimes apply depending on where you send and what kind of message you send: US application traffic needs 10DLC, every recipient can opt out, and many countries gate alphanumeric senders behind pre-registration. You file each once and check its status from the same client you send with.
Which regime applies to me?
What you have to register depends on where your recipients are and what you send. Most US application programs touch all three at once.
| Regime | What it covers | Where it applies |
|---|---|---|
| A2P 10DLC | Brand and campaign registration for application-to-person traffic | United States |
| Opt-out (STOP/HELP) | STOP, HELP, and START keyword handling and a suppression list | Everywhere you send |
| Sender-ID registration | Pre-registering alphanumeric sender IDs before they can deliver | Many countries that require it |
File once, check status
from the API.
You submit a 10DLC brand and campaign, a toll-free verification, or a sender-ID registration from the dashboard. Bird carries it to the carriers and registries and exposes the current state through the API, so your provisioning code can wait for approval rather than guess at it. Opt-out handling needs no setup: it's enforced on every send.
Compliance, by regime
Each regime in depth: what it requires and how Bird files and tracks it.
The rest of the SMS platform
One API, one set of keys. Explore the other capabilities.
Register once, send with confidence.
Compliance is one capability of the Bird SMS API: sending, numbers, two-way inbound, routing, and analytics ship with it.