Logged into developers.monzo.com (fresh magic-link login, cleared cookies for monzo.com/auth.monzo.com first), navigated to Clients. The page loads but “Your OAuth Clients” stays empty. DevTools Console shows:
Failed to load resource: the server responded with a status of 403 () — api.monzo.com/accounts
Failed to load resource: the server responded with a status of 403 () — api.monzo.com/oauth2/clients
The server response was not OK: Response Object (apps.js:41)
This happens consistently across two networks, both in normal Chrome and Incognito (ruling out extensions), on desktop. I’ve never successfully created an OAuth client — the “New OAuth Client” form appears to submit but nothing ever shows up in the list afterward, which now looks like it’s this same 403 rather than a form bug. Similar reports: oauth-clients-not-accessible, authentication-broken.
Update - still an issue as of 18 Sept 2026
Bumping this as I’m still hitting problems, though it’s evolved a bit.
Creating the OAuth Client itself failed silently a few times (submit form → just bounces back to “Manage OAuth Clients” with nothing added, no error) - what actually got it to work was opening the Monzo app and approving an access request notification that popped up there. After that the client did exist.
But then a new problem: going through the actual sign-in flow (auth.monzo.com), the page just hangs on a blank loading spinner, nothing happens. Tried it twice, including a fresh incognito window on a brand new link, same result both times. My own app/listener side was working fine and just sat there waiting the whole time, so it’s definitely something not completing on Monzo’s end.
Anyone else still seeing this, or has anyone from Monzo actually looked into it? Feels like the same underlying issue as some of the other threads here (403s on oauth2/clients, “Authentication Broken?”) rather than anything client-side.