Deliver SMS reliably across countries and mobile carriers.

Send order updates, appointment reminders, and account alerts to customers across global mobile networks through one API. Bird checks your enabled destination countries and sender requirements before handoff, routes messages to the recipient's carrier, and reports real-time delivery receipts and failure reasons so you can spot carrier filtering or registration gaps fast.

Get StartedContact Sales

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.

  1. 01

    Control 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.

  2. 02

    Validate 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.

  3. 03

    Price 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.

  4. 04

    Track 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.

  5. 05

    Plan 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.

POST /webhooks/bird
signed
{
  "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
    }
  }
}

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.deliveredThe destination carrier confirmed that the message reached the recipient's handset.
  • sms.failedThe message could not be delivered, including the normalized failure reason and any raw carrier error code.

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?
Open the destination catalogue and review the sender types and registration requirements for each market. Your workspace must also allow the destination before a send is accepted.
What does a carrier receipt establish?
It reports a delivery outcome from the carrier. Receipts can arrive after acceptance, and the message record may still be pending. Delivery does not measure whether someone read or acted on a text.
How should I investigate a failed route?
Start with the message status and failure reason. Compare reporting by carrier, country or sender, then check registration and destination configuration. An aggregate failure rate alone does not identify the cause.
Can I inspect a phone number separately?
Use Lookup when your application needs phone-number intelligence before sending. Review the signals and availability for that lookup rather than treating an SMS delivery report as a complete number check.

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.

Organize teams in workspaces, control API access, and trace changes through audit logs.

WorkspacesTeam rolesAPI authentication
Explore Enterprise

Start with SMS.
Build across channels with Bird.

Get StartedContact Sales

Start building with Bird in minutes.

Get StartedContact Sales