Numbers

The right sender for every message.

Choose a number or sender ID for the message you need to send. Check the capabilities, destination and registration requirements together. Search and order eligible numbers through Bird; work with an SMS specialist for short-code allocation.

Start for Free Contact sales

CursorCopied!

A local number

Conversations and notifications

A toll-free number

An SMS-capable national identity

A short code

An approved messaging program

Your brand name

One-way messages where supported

Choose by destination, capabilities and registration requirements.

Trusted every day by teams that build world-class software

Four sender types, one API.

Numbers are the foundation of the Bird SMS API. Search availability, buy a number, and route inbound to a webhook with the same client you already send with. Which type you pick depends on volume, geography, and how much registration you can take on.

Which sender should I use?

Throughput, reach, and registration effort differ by sender type. Most US application traffic starts on a 10DLC long code; high-volume one-to-many programs move to a short code.

Sender type	Best for	Registration
Long code (10DLC)	Two-way conversations, OTP, alerts at moderate volume	A2P 10DLC brand + campaign
Short code	High-volume one-to-many marketing and alerts	Carrier-vetted, lead time in weeks
Toll-free	US/Canada messaging through the toll-free verification program	Toll-free verification
Alphanumeric sender ID	One-way branded alerts where the country allows it	Pre-registration in many countries

Pick a number type

Each sender type in depth: reach, throughput, and what it takes to register.

Long codesSMS-capable local numbers, with 10DLC registration for US application traffic.Short codesShort national numbers for a reviewed, high-volume messaging program.Toll-freeVerified toll-free numbers for US and Canada traffic without 10DLC.Alphanumeric sender IDsSend from your brand name where the destination country allows it.SMS resource libraryFind guides, explained answers and tools for your next step.

Search, buy, and route in a few calls.

Find a number by country and capability and buy it, from the same SDK you send with. Inbound traffic is routed by a workspace webhook subscribed to sms.received rather than per number, so one subscription covers every number you hold. The number is live as soon as any required registration clears.

provision.ts

201 · purchased

const { data: page, error: searchError } = await bird.numbers.available
  .list({
    country_code: "US",
    number_type:  "local",
    capabilities: ["sms"],
  })
  .safe();
if (searchError) throw searchError;

const { data: order, error: orderError } = await bird.numbers.orders
  .create({ number: page.data[0].number })
  .safe();
if (orderError) throw orderError;

console.log(order.status, order.number_id); // → "completed" "nda_0ydh2yfw..."

Registration, handled where it's required.

Most US application traffic needs A2P 10DLC brand and campaign registration; toll-free needs verification; many countries require sender-ID pre-registration. Bird runs each of these from the dashboard, and the compliance surface tracks status from the API.

Questions about this sender

Which number type should I start with?

Choose by destination, required capabilities, traffic pattern and registration. A number’s type describes its network category; its capabilities tell you whether that number can carry SMS or voice.

Does owning a number mean I can send immediately?

No. Ownership, sender registration and an enabled destination are separate checks. A number can be allocated while compliance work is still outstanding.

Can I buy a short code in the numbers API?

No. Short codes are allocated by Bird through an assisted process. Ask an SMS specialist to review the market, program and traffic requirements.

Can one number carry SMS and voice?

Yes, when the allocated number lists both capabilities. Filter inventory by the capabilities you need and check the returned number; do not infer them from its type alone.

Put it into practice.

Continue with the documentation, guides and examples for this topic. Resources are in English.

Watch the guideRegistering your SMS sender ID Understand the conceptWhat is sender ID registration, and why do some countries require it?Follow the learning pathBuild your first integration Explore the capabilitySMS sender IDs

Get an implementation brief

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.Two-wayInbound SMS and conversational replies as HMAC-signed webhooks.ComplianceA2P 10DLC registration, opt-out keywords and sender-ID rules.RoutingDestination controls, carrier handoff and delivery evidence.AnalyticsDelivery outcomes, failure reasons and latency from carrier receipts.SMS API overviewThe full SMS API: sending, numbers, two-way, compliance, routing, and analytics.

The right sender for every message.

Four sender types, one API.

Which sender should I use?

Pick a number type

Search, buy, and route in a few calls.

Registration, handled where it's required.

Questions about this sender

Put it into practice.

The rest of the SMS platform

Choose a sender with a clear path to launch.

Your details

Products of interest

Start with one channel.
Add the others when you're ready.

The right sender for every message.

Four sender types, one API.

Which sender should I use?

Pick a number type

Search, buy, and route in a few calls.

Registration, handled where it's required.

Questions about this sender

Put it into practice.

The rest of the SMS platform

Choose a sender with a clear path to launch.

Your details

Products of interest

Start with one channel.Add the others when you're ready.

Start with one channel.
Add the others when you're ready.