Compliance

The rules, handled in one place.

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.

send-otp.ts

200 · 0.4s

import { BirdClient } from "@messagebird/sdk";

const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });

const code = generateOtp();

const { data, error } = await bird.sms.send({
  from: "Bird",
  to:   "+15005550006",
  text: `Your Bird verification code is ${code}. Reply STOP to opt out.`,
}).safe();

if (error) throw error;
console.log(data.id);
// → "sms_4kT01Lq2m..."

import { BirdClient } from "@messagebird/sdk";

const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });

const code = generateOtp();

const { data, error } = await bird.sms.send({
  from: "Bird",
  to:   "+15005550006",
  text: `Your Bird verification code is ${code}. Reply STOP to opt out.`,
}).safe();

if (error) throw error;
console.log(data.id);
// → "sms_4kT01Lq2m..."

send-otp.ts

200 · 0.4s

import { BirdClient } from "@messagebird/sdk";

const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });

const code = generateOtp();

const { data, error } = await bird.sms.send({
  from: "Bird",
  to:   "+15005550006",
  text: `Your Bird verification code is ${code}. Reply STOP to opt out.`,
}).safe();

if (error) throw error;
console.log(data.id);
// → "sms_4kT01Lq2m..."

import { BirdClient } from "@messagebird/sdk";

const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });

const code = generateOtp();

const { data, error } = await bird.sms.send({
  from: "Bird",
  to:   "+15005550006",
  text: `Your Bird verification code is ${code}. Reply STOP to opt out.`,
}).safe();

if (error) throw error;
console.log(data.id);
// → "sms_4kT01Lq2m..."

Three regimes, one surface.

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

Compliance, by regime

Each regime in depth — what it requires and how Bird files and tracks it.

A2P 10DLCBrand and campaign registration for US application traffic.Opt-out (STOP/HELP)STOP, HELP, and START keywords honored automatically, with a queryable suppression list.Sender-ID registrationPre-register alphanumeric sender IDs where countries 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.

SMS compliance FAQ

What do I have to register before I can send?+

It depends on where you send and what you send. US application traffic needs A2P 10DLC brand and campaign registration. Many countries require sender-ID pre-registration for alphanumeric senders. Opt-out handling applies everywhere and needs no setup.

Do I have to build opt-out handling myself?+

No. STOP, HELP, and START keywords are honored automatically on every send. A STOP suppresses the recipient, HELP triggers a help response, and START resubscribes them. The suppression list is queryable through the API.

How do I know when a registration is approved?+

Bird files each registration with the carriers or registries and reports its status through the API. Your code can poll the registration's state and wait for approval rather than send into a campaign that isn't live yet.

Is compliance separate from the rest of the SMS API?+

No. It uses the same client and keys as sending, numbers, and two-way. Registration status and the suppression list are API resources alongside the send call, so one integration covers both sending and the rules around it.

The rest of the SMS platform

One API, one set of keys. Explore the other capabilities.

SendingThe send API: segments, Unicode safety, batch, and idempotency.NumbersLong codes, short codes, toll-free, and alphanumeric sender IDs.Two-wayInbound SMS and conversational replies as HMAC-signed webhooks.Routing150+ countries, 240 direct-to-carrier links, and failover.AnalyticsDelivery and engagement metrics from carrier delivery receipts.SMS API overviewThe full SMS API: sending, numbers, two-way, compliance, routing, and analytics.

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.

Explore the SMS platform Get started