Can't send OTPs with MessageBird for Auth - access key invalid

[katherineqian]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I keep receiving the 422 response Request not allowed (incorrect access_key) even when a cURL request with the same access key from MessageBird is succeeding.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to https://app.bird.com/settings/security/access-keys to generate an access key as described in the docs.
2. Get an access key with permissions for creating and viewing from /workspaces/*/channels/*/messages as described in Messagebird docs.
3. Try making a cURL request to send a text message with the generated key. Observe that the request succeeds.
4. Try sending an auth OTP using the same key entered into the Supabase dashboard. Observe that the request fails with Request not allowed (incorrect access_key).

Expected behavior

OTP should send to the desired phone number if the access key is working elsewhere.

Screenshots

N/A

System information

• OS: Flutter on MacOS
• Browser (if applies) [e.g. chrome, safari]: N/A
• Version of supabase-js: Using supabase_flutter: ^2.3.4
• Version of Node.js: N/A, using supabase_flutter: ^2.3.4

Additional context

Add any other context about the problem here.

[MichaelKirsch]

Same problem here

[kangmingtay]

Hey @katherineqian and @MichaelKirsch, it seems like the change from messagebird to bird caused the integration to break here - the messagebird SMS provider was added quite awhile back (#210) and is only compatible with the old API.