Make the first SMS
an informed one.
Check country, sender, recipient and segment cost before the documented API path. Create your API key, test a controlled message and follow its events after acceptance.
Companies that trust Bird across their communications.
Read Bird customer storiesA setup path with a recoverable stop.
Compare an eligible plan with a registration-pending case. Credentials and exact request fields remain in the maintained guide.
Four checks before the API.
- 01Destination and allowlistVerify account access, intended country and local message category.
- 02Sender and registrationHold an eligible sender and complete required review before using the production identity.
- 03Audience and costCheck permission, preferences and reply needs. Count encoded segments and add applicable fees.
- 04Observe and recoverKeep the message ID and original idempotency key. A 202 begins processing; inspect later delivery events.
Pick a setup state.
US: confirm sender, recipient permission, category and allowlist. Follow the maintained sending guide. Record the accepted message ID and original idempotency key, then inspect the log and later receipt.
Local checklist only. No API request is made, and the selected state does not establish account eligibility or delivery.
Fictional setup states. Credentials and exact requests remain in the maintained sending guide.
See what happens after send.
Track each message from API acceptance through the delivery events Bird receives. Connect those updates to your application so your team can spot failures and follow up.
Build delivery tracking ↗Prepare a test you can learn from.
Prepare the sender and destination, then test the complete delivery path.
Sign up for Bird.
Create your account and an API key. Keep the key on your server and configure the workspace your application will use.Choose the country and sender.
Check which sender types your destination accepts, then choose a name or number. If customers need to reply, choose a suitable number. Read the sender guide →Follow the registration path.
Read the sender’s country requirements and complete any required review. For a US long code, follow the brand, campaign and number registration path. Destination requirements · US 10DLC guidePrepare the recipient and reply handling.
Enable the destination in your workspace, confirm recipient permission and prepare the opt-out flow for your messages. Opt-outs and keywordsTest the send and its outcome.
Use the supported sandbox recipient to test the lifecycle; it still requires the appropriate US sender and destination setup. A send to your own phone is a real SMS. Verify signed events and handle failures before sending to customers. Sending and testing guide → · Delivery receipt example
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Questions before your first send
How do I test my SMS integration?
What does Bird SMS include?
Which countries can I send to?
When do I need 10DLC registration?
Choose your next step
Build the supported first path.
Confirm the destination, sender and account requirements, then follow the maintained guide for your next step.
Build the next part of your SMS workflow.
Set up your sender and destination, test the send and use delivery events to check the integration before messaging customers.