Send appointment reminders, run opted-in campaigns or handle customer replies. Choose the SMS workflow that fits your business, then set up its sender and destinations.
The same SMS API can serve different messages. Start with the job, then check eligibility and local sender rules before an integration choice.
Send a timely booking, account or service update from your application. Consent and message category still matter.
Plan a permissioned audience, suppress withdrawals and review segments and timing before a supported send.
Receive a reply on a supported number, verify the event and let your application confirm the customer task.
Bird / SMSGSM-7 · 62 units · 1 estimated segment
Follow the messageExample · no request is madesms_example_fn1042
The illustrative request was accepted by Bird.
The illustrative message was handed to the carrier.
sms.delivered
Record the carrier receipt. It does not establish that Alex read the message, replied, or confirmed the booking.
Local illustration. No request is made.
Inspect the message outcome ↗Your applicationRecord the carrier receipt. It does not establish that Alex read the message, replied, or confirmed the booking.
Example content and data. Explore the workflow below; nothing is sent or changed in a live account.
Companies that trust Bird across their communications.
Read Bird customer storiesEnable each destination in your workspace allowlist. Sender types, registration, message categories and reply support vary by country. The current destination details is the authority; Netherlands and United States are examples to inspect there, not a substitute for current approval or account access.
Explore three country examples ↗Read the sender guide for number or sender ID selection and registration. A displayed name cannot receive replies; a two-way workflow needs a supported receiving number and an application path for inbound messages.
Read sender setup ↗Review three dated country examples, then confirm allowlist, category, sender and reply support in current details.
Try the local segment estimator, then open the SMS API implementation and maintained sending guide.
Keep the message ID and observe later carrier outcomes. A receipt is not proof of reading or booking success.
Start, build, diagnose, migrate or evaluate with current guides, references and tools.
Explore SMS resources →Prepare your sender, run a complete Node.js example and read the outcome.
Use the maintained sending contract and follow its result.
Check a standalone message draft, character map and smart encoding before reviewing rates.
Preview a message and segment estimate in the local SMS API story.
SMS is charged per segment, with rates and fees depending on destination and sender. The composer estimates encoding and segment count; it is not a worldwide quote. Confirm registration, coverage or volume with our team.
Check current SMS rates ↗Decide the use case, then check the maintained rules for every market.
No. Reply support depends on destination and sender type. Use a supported two-way number and route incoming messages into your application. Read sender setup.
Verify owns the separate verification lifecycle: code creation, attempts, expiry and checking. A normal SMS send does not supply those controls.
No. GSM-7 extension characters and Unicode can change encoding and length; multipart messages reserve header space. Estimate segments, then check current rates.
Una chiave API di test è subito tua. La produzione si sblocca quando aggiungi un metodo di pagamento e verifichi un mittente.
Leggi la documentazione