MessageBird · Bird
MessageBird integration in your app
MessageBird integration means your events — “order sent”, “code” — go out as SMS or another channel via Bird, with status back in your log. Choose it if you already have a Bird account, or if you know WhatsApp and more channels are coming within a year. Choose [GatewayAPI](/articles/integrations/gatewayapi-integration) if you only need Danish SMS this year. Bird is the same category as [Twilio](/articles/integrations/twilio-integration). Not the same API. We integrate what you have an account with — we do not start three gateways. Consent, retry, log and never a CPR number in the message apply here as everywhere else.
A channel is not the same as an event. “Order sent” is your truth. SMS or WhatsApp is a pipe. Keep the pipe swappable. Automation that owns the event.
When Bird is the right socket
- You already have a Bird account and keys
- WhatsApp or more channels are on the roadmap within a year
- You do not want to open Twilio “next to it” for the same job
Choose Bird
- Existing account
- Several channels within a year
Choose something else
- DK SMS only: GatewayAPI
- Voice + global, you are on Twilio: stay
What to do now
Tell us whether you already have Bird, and whether WhatsApp is a requirement or a wish. Then we pick the socket.
FAQ about MessageBird integration
Is it the same as Twilio?
Same category. Not the same API. We integrate what you have an account with — we do not start three gateways.
Do we need WhatsApp in version 1?
Only if you can point to customers who refuse SMS. Otherwise it is an add-on that delays launch.
Is it MessageBird or Bird?
In the docs: the name your login still uses. In your UI: what you want on the receipt.