SMS routing.
Route customer texts across countries with sender checks before handoff to the carrier.
Accepted
+44 7700 900123 · Destination and sender checks passed
Sent
+44 7700 900123 · Northstar Mobile
Delivered
+44 7700 900123 · Delivery receipt · Northstar Mobile
Reach global mobile networks through one integration.
Instead of stitching together regional aggregators or guessing why a text disappeared in transit, send through the Bird SMS API. Bird checks that the destination country is enabled for your workspace and that your sender meets local rules before accepting the message, or selects a compliant sender automatically when you use a built-in template. Once handed off to the mobile network, each message record tracks the handling carrier and delivery status from acceptance to handset.
Catch destination and sender issues before carrier handoff.
Protect your SMS budget with workspace country controls, upfront sender checks, and carrier-level visibility.
01Control which countries your workspace can message.
Prevent unexpected international traffic or toll fraud with a default-deny destination allowlist. Enable the countries your business serves in your workspace settings, and check supported sender types and registration rules in the destination catalogue before launching.02Validate sender compliance before messages are queued.
Whether a market requires a registered alphanumeric sender ID, a US 10DLC number, or a verified toll-free number, Bird checks sender eligibility before accepting your request so misconfigured traffic fails fast instead of dropping silently at the carrier.03Price and route to ported numbers accurately.
Phone prefixes no longer tell you which mobile network a subscriber uses after they port their number. Bird resolves operator information during processing when available, falls back to country pricing if a lookup is unavailable, and records the handling network reported on the receipt.04Track message status from acceptance to handset.
Follow each message through its timeline as it moves from accepted to sent and on to a terminal carrier receipt such as delivered, undelivered, failed, or expired. When a carrier omits network details or a receipt is still pending, the timeline shows the exact state reported so far.05Plan high-volume rollouts with our SMS team.
Messages travel over Bird's managed carrier routes without requiring per-request route selectors in your payload. When you are scaling into new markets or planning high-throughput campaigns, work with an SMS specialist to align your destination mix, sender registrations, and throughput.
Pinpoint why a text failed without guessing.
When a customer misses an order alert or delivery drops in a new market, you need to know right away whether the handset was switched off, the phone number is unassigned, or a carrier filtered an unregistered sender. Bird combines destination requirements, per-message timelines, and normalized failure reasons in one workflow so your team can fix sender registrations or clean up invalid numbers fast.
Receive carrier delivery receipts and network details in real time.
Because carrier delivery happens asynchronously after Bird accepts your request, signed webhook events stream each status change back to your app. Use the reported carrier, network code, and failure reason to trigger an email fallback, pause sends to bad numbers, or spot a degraded carrier route.
Webhook payloads include the handling carrier and mobile network code when reported by the operator. If network details are omitted by the upstream carrier or differ from a number's original prefix, inspect the message timeline in the SMS log for the available event history.
sms.delivered- The destination carrier confirmed that the message reached the recipient's handset.
sms.failed- The message could not be delivered, including the normalized failure reason and any raw carrier error code.
{
"type": "sms.delivered",
"timestamp": "2026-05-19T15:42:01.221Z",
"data": {
"sms_id": "sms_4kT01Lq2m",
"workspace_id": "ws_8KQ2",
"to": "+15005550006",
"from": "+12025550188",
"tags": null,
"metadata": null,
"carrier": "Verizon",
"mcc_mnc": "311480",
"cost": {
"amount": "0.0079",
"currency_code": "USD",
"transaction_amount": "0.0079",
"passthrough_amount": null
}
}
}
Validate phone numbers and automate failure handling.
Check phone number formatting and line intelligence before you send with Lookup, and subscribe to signed webhooks so your backend can react to delivery outcomes automatically. A number lookup helps catch invalid inputs early, though it does not replace sender registration or guarantee carrier delivery. Use the error reference and deliverability guide to troubleshoot carrier blocks and registration issues.
Questions before you build
How do I check destination coverage?
What does a carrier receipt establish?
How should I investigate a failed route?
Can I inspect a phone number separately?
The rest of the SMS platform
Provision sender numbers, receive customer replies, and monitor carrier delivery from the same workspace.
- SendingSend order alerts, appointment reminders, and batch notifications with safe retries.
- NumbersSend from local long codes, toll-free numbers, short codes, and brand-name sender IDs.
- Two-wayReceive customer replies for appointment confirmations and support threads on the same number.
- ComplianceManage US 10DLC registration, country sender rules, and automatic STOP opt-outs.
- AnalyticsTrack delivery rates, carrier failure reasons, and time-to-delivery across countries.
- SMS API overviewSee how sending, numbers, two-way replies, compliance, and analytics fit together.
- SMS resource libraryBrowse implementation guides, country rules, and interactive SMS tools.
Scale without losing control.
Separate production and sandbox traffic into dedicated workspaces, scope API keys to the exact channels each service or agent needs, and track permission changes in the audit log.