Anyone else having issues with OAuth authentication? While attempting to obtain an Authorization Code, Monzo is stumbling attempting to send the magic link for login with the error “Unknown error”.
The configuration of the URLs/Client ID/Client Secret/etc. are correct as this has been working for many months now.
I’ve also attempted to setup a new OAuth client to test via Postman and get the same error.
4 Likes
Looking at browser dev tools, the actual error is “No user with that email address was found” even though
- as mentioned previously, this was working before
- I can log in to the developer playground with the same email address (interestingly, the dev playground also authenticates via OAuth but it must be using a different system. Odd.)
So it looks like the issue lies with Monzo but it would be nice to have confirmation from someone else that utilises the API.
Side note, it’s also a bug that Monzo displays “Unknown error” when the error is clear from the JSON payload. Perhaps it’s related?
2 Likes
Hey,
Yes I am also receiving the same error, where the Magic Link is showing an “Unknown Error” when submitting the correct email upon authentication.
I’ve submitted a request through the app to see if they can help fix the issue, but haven’t heard anything back yet.
2 Likes
Yes it is broken for me too … & same error “no user for email found”
1 Like
Exact same issue for me, I’ve changed nothing with my config, tried to create a new token and the same error. This project has worked fine for years, glad to see it’s not my end. I’ve reported in app too a few weeks back but haven’t heard anything.
2 Likes
An update from support, they have literally told me to come back to the community forums and find an answer…
Do any of the Monzo devs look at these pages?
Still having the same issue.
2 Likes
Same issue as above. Dev playground works fine.
I checked my client details are all correct, even recreated it, but I cannot login using Oauth for my personal app.
1 Like
How tf is this still broken after 22 days
1 Like
Hey! Thanks for raising this.
Sorry for the disruption. We’ve investigated and put a fix in place - let us know if you see anymore problems 
6 Likes
@WilliamRay Thank you, this is working again! 
2 Likes
Is this fixed? Mine still saying unknown error
@WilliamRay Thank you for this, can confirm it works now
Hey all - I am experiencing this behaviour today - is there something wrong with this system at the moment? can’t generate an access token and getting a 403 Cloudfront error instead of retrieving my code to authenticate.
Same for me, was about to create a new topic. I noticed that if I don’t use http:// in front of my redirect URI, I get past the 403 error, but then I still get “Unknown error” when Monzo tries to send the magic link.
Yep same noticed that too - status says the API is operational though…
+1 also happening for me.
I had a script fail to save the refresh token and needed to get a new one manually but can’t. I’m new to the Monzo API and haven’t found it very reliable. Does anyone here use another bank that has a good API?
Starling do https://developer.starlingbank.com/
Hi, I’m currently getting 403 responses on the API on both listing transactions and trying to authenticate with both my existing application and a new one I set up to test. This has been running fine for the past few years however now it’s no longer working.
This is what I’m getting when trying to authenticate:
I have double checked both the client_id and redirect uri and they 100% match.
Is anyone else having problems?
Thanks
1 Like
+1 happening to me as of the weekend just gone (but I only test this on a weekly basis). It was working fine last weekend but am unable to now authenticate now that my token has expired
Step 1 of authentication step fails with this 403.
@WilliamRay could your team please investigate again?
Hey @tom493 
I checked with the team and we think this should be fixed now. Can you try again and let us know if you’re still having issues?
We’ll take another look if you are 