-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't send OTPs with MessageBird for Auth - access key invalid #1554
Comments
Same problem here |
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. |
hello there is there a fix fro this ? |
any fixes for this? |
Hi everyone, as mentioned previously, there seems to be some incompatibility between MessageBird's API and their API after they rebranded to Bird. We recently launched a hook for sending SMS, if you want to use Bird as the SMS provider, you can use the hook to directly make requests to their API endpoint. Here are some links which may be useful: |
Hey team, Going to close but feel free to comment, or open a ticket if there are any issues with implementing the provider. |
Would love to see this fixed for the new API! |
Me too! |
Bug report
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:
/workspaces/*/channels/*/messages
as described in Messagebird docs.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
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: