Communication · Integration
MessageBird
Add MessageBird to your product for your customers, and give your AI agents governed access to it.
MessageBird, now trading as Bird, exposes several separate APIs on different hosts: rest.messagebird.com for SMS, contacts and groups, conversations.messagebird.com for the omnichannel inbox, and voice.messagebird.com for calls. Authentication uses an Authorization header with the AccessKey prefix rather than Bearer, and live and test access keys are distinct, with test keys accepting requests but never delivering anything. Outbound SMS needs an originator that is valid for the destination country, and alphanumeric sender IDs are rejected or rewritten in countries such as the United States, which is the most common cause of messages that report as sent but never land. Long messages are split into concatenated parts and billed per part, and the message object reports recipients with individual status values rather than one status for the whole send. The Conversations API models a customer as a contact with channel-specific identifiers, so the same person on SMS and WhatsApp is one conversation only if the contact is matched. fastn keeps each customer's access key and channel configuration isolated and maintains the connection over time.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own MessageBird account so messages are sent from their numbers and billed to them
Send SMS or WhatsApp notifications from your product with per-country originator handling
Sync contacts and groups so your segments stay aligned with their messaging lists
Show per-recipient delivery status and inbound replies inside your own conversation view
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent reply in an existing conversation but require approval before starting an outbound campaign
Have an agent check delivery status and failure reasons for a batch, audited per tenant
Restrict an agent to a single originator or channel so it cannot send from another team's number
Example prompt
Did the verification SMS we sent through MessageBird to this number get delivered?
Set up MessageBird in 4 steps
- 01Enable the MessageBird connector from your fastn dashboard.
- 02Have each customer authorise their own MessageBird account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the MessageBird integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a MessageBird integration without building it. Your customers connect their own MessageBird account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a MessageBird update is not your on-call problem.
- One integration serves your product and your agents. The same governed MessageBird connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to MessageBird, across other categories.
MessageBird integration FAQ
How do I add a MessageBird integration to my product?
Enable the MessageBird connector in your fastn dashboard, then let each customer authenticate their own MessageBird account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no MessageBird client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own MessageBird account?
Yes. Every connection is scoped to the individual customer, so each authorises their own MessageBird account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this MessageBird integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent reply in an existing conversation but require approval before starting an outbound campaign
Who maintains the MessageBird integration?
fastn does. When MessageBird changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own MessageBird account?
Yes. Every customer authorises their own MessageBird account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the MessageBird integration?
A common starting point: let a customer connect their own MessageBird account so messages are sent from their numbers and billed to them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the MessageBird integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding MessageBird does not change your per-connector cost. You can start free with 3 connected accounts.
Add MessageBird to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.