SMS
for developers

Send codes and updates. Receive replies.
Build SMS into your app with Bird’s API.

Get startedContact Sales

Trusted every day by teams that
build world-class software.

Read customer storiesExplore Enterprise

From prompt to delivered.

Send an SMS from your app or agent. Follow the carrier receipt.
Full read and write access through MCP and CLI.

YouSMS

Text the code 123456 to +14155550100 from +15557654321 and check the delivery status.

Bird MCP4 connected actions
  1. 1Read the workspaceworkspace_get
  2. 2Send the SMS codesms_send
  3. 3Read the message statussms_get
  4. 4Check the delivery eventsms_list_events
Explore MCP docs →
United States
+1 (202) 555-0188Dedicated number
Replies
Send and receive
Registration
10DLC
Registration required

Register your brand and campaign, then link your number.

Start with the right sender.

Choose an identity for the destination. See which registrations you need and which numbers can receive replies.

Explore SMS senders
Message body

Your order is on its way. We'll deliver tomorrow between 10:00 and 12:00. Reply CHANGE if you need another time.

Smart encoding
1segment
GSM-7

One apostrophe. One fewer segment.

Make every character count.

One curly apostrophe adds a billable segment here. Opt in to smart encoding to bring it back to one.

Explore smart encoding

Turn incoming texts
into useful replies.

Receive texts on an eligible number. Reply from your app,
or connect the steps in a Bird automation.

Acknowledge an incoming SMSAutomations
Published
One message. Every step connected.
  1. 01
    Message received

    “Is my order ready?”

    Bird event
    Received
  2. 02
    Recognize sender

    Match by phone number

    List contacts → Branch
    Waiting
  3. 03
    Send a reply

    Personal acknowledgement

    Set values → Send SMS
    Waiting
  4. 04
    Confirm delivery

    Wait for the SMS receipt

    Wait for event → Exit
    Waiting
Other paths No match, failures & timeout

No contact foundContinue with a generic greeting.

Lookup failed or multiple matchesExit and record the reason.

Send failedClassify the failure.

No receipt within 10 minutesRecord delivery as unconfirmed.

Incoming SMS

Is my order ready to collect?

Received
Incoming SMS events
Explore Automations
Illustrative SMS reply workflow. Send acceptance is followed by a carrier delivery receipt, not a read receipt. No messages are sent from this page.

Before you ship.
After you send.

Preview requests, follow delivery, and fix errors with clear feedback.

CLI dry run
bird sms send \
  --from +15557654321 \
  --to +14155550100 \
  --text 'Your verification code is 123456.' \
  --category authentication \
  --dry-run
SMS · Request preview

Preview before you send.

Inspect the CLI request before it reaches the API.

Explore CLI dry runs
POST /webhooks/bird Signed
SMS delivered

Its signed event is ready for your endpoint.

Endpoint response

Know what happened.

Follow delivery receipts and incoming texts through signed events.

Explore webhooks
POST /v1/sms/messages
Idempotency-Keywelcome/customer_42
Original request202 Acceptedid: sms_01ky7q3hckecgv6d7jpq865532status: accepted
Same request · retry 01202 Acceptedid: sms_01ky7q3hckecgv6d7jpq865532Idempotency-Replay: true
Same request. Same result.

Recover the response.

Retry with the same key to recover the original response.

Explore idempotency
POST /v1/sms/messages
422E01001 ValidationError

to must be a phone number in E.164 format.
Include the country code, starting with +.

req_01ky7q4665emc9tw1pxkptaqwqError reference

Errors you can act on.

The field, the reason, and the correction. Then try again.

Explore errors
Illustrative product states. No messages are sent from this page.

Every message.
A clearer picture.

Follow delivery over time. See which carriers account for failures.

SMS analytics

Delivery over time

37,380accepted98.0%delivery rate
Delivery over timeIllustrative hourly SMS analytics for September 21. Accepted, Delivered and Failed outcomes share a count axis. Figures are illustrative, not live account statistics.07501.5k2.3k3kMessages00:0004:0008:0012:0016:0020:0023:00
AcceptedDeliveredFailed
Sep 21 · UTC
74.1%

of failures in this hour
Northstar Mobile

206 of 278 · 14:00–15:00 UTC

By carrier

14:00–15:00 UTC
CarrierAcceptedFailedShare
1,52920674.1%
8345018.0%
417227.9%
Explore SMS analytics

Explore SMS.

From your first sender to two-way conversations. Build SMS into your app.

SMS API

Send text messages from your application and inspect the result.

Senders

Choose a sending identity that works for the destination.

Two-way SMS

Receive customer texts and reply from your application.

Templates

Send reusable texts with variables and language selection.

Automations

Receive a text, find the customer, and send the next reply.

Global delivery

Understand destination support before sending.

Encoding & segments

See how characters affect message length and segment count.

Consent & opt-outs

Honor the choices customers make about your messages.

Webhooks

React to incoming texts and delivery changes.

Analytics

Understand SMS delivery by carrier and destination.

Scale without
losing control.

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

BirdHarborOrganization
WorkspacesProductionSandbox

Delivery agent

API key · Customer operations team
Active
PermissionsAccess
EmailRead & write
SMSRead & write
ALAlex Lee AdminPermissions updated

Audit log

Production
Workspace
Production
Resource
Delivery agent
WhatsApp
ReadRead & write
Succeeded
WorkspacesTeam rolesAPI authentication
Explore Enterprise

Start with SMS.
Build across channels with Bird.

Get startedContact Sales

Your next idea.
Ready to connect.

Get startedContact Sales