Coming from MessageBird
If you used MessageBird before, that account still exists and works as it always has. It's separate from an account you create at bird.com, even when both use the same email address. Your MessageBird credits and API keys stay with your MessageBird account.
Where do I sign in?
Sign in where your account was created:
| Account | Sign in at |
|---|---|
| MessageBird, now called Connectivity Platform | dashboard.messagebird.com |
| Bird Engagement Platform, or Bird CRM | app.bird.com |
| bird.com | bird.com/dashboard |
The bird.com sign-in page links to both older platforms.
Can I use my MessageBird credits on bird.com?
No. Credits you bought on MessageBird stay on your MessageBird account, and you can keep spending them there. We can't move them to a bird.com account. If you have a question about a MessageBird balance, contact support.
bird.com doesn't use credits. You pay for messages from your organization's wallet, which you fund with top-ups or a plan. Payment methods and wallet explains how it works.
Do my MessageBird API keys work on bird.com?
No. A MessageBird access key works with the MessageBird API at rest.messagebird.com. bird.com has its own API, with keys that start with bk_, and those keys don't work on the MessageBird API either. Authentication and API keys shows how to create a bird.com key.
Which platform does my API call belong to?
Match the host in your code to its platform. A key works only on the API of the platform that issued it.
| Your call goes to | Platform | Key and header |
|---|---|---|
https://rest.messagebird.com/... | MessageBird, now called Connectivity Platform | A MessageBird access key, sent as Authorization: AccessKey |
https://api.bird.com/workspaces/{workspaceId}/..., such as POST /workspaces/{workspaceId}/channels/{channelId}/messages | Bird Engagement Platform, or Bird CRM | An access key created at app.bird.com, sent as Authorization: AccessKey |
https://us1.platform.bird.com/v1/... or https://eu1.platform.bird.com/v1/... | bird.com | A key that starts with bk_, sent as Authorization: Bearer |
A bird.com key does not work on api.bird.com or on rest.messagebird.com, and an access key from either older platform does not work on bird.com. The Engagement Platform API docs describe the api.bird.com API, and Base URLs and regions lists the bird.com hosts. The Engagement Platform guides describe that platform as retired. They are kept for customers still running on it, and they are not maintained.
Why doesn't the MessageBird option in my tool work?
Some tools have MessageBird built in as an SMS provider. Supabase's phone sign-in is one of them. These connect to the MessageBird API with a MessageBird access key, so they don't work with a bird.com account.
With a bird.com account, use Verify to send sign-in codes, or send SMS with the SMS API from your own code. For Supabase, send the sign-in codes through Bird with Supabase's Send SMS Hook.
How do I move my SMS integration to bird.com?
Follow Migrate SMS from Bird Connectivity Platform. It maps each field of the MessageBird API to the bird.com API, and explains how support moves numbers you want to keep.
Next steps
Related resources
Continue with the documentation, guides and examples for this topic.