Hello
Recently the /transactions endpoint returns a 403 asking for verification from my mobile app. This is quite a unusual flow as:
- I already previously approved access on the app for the original access token… (which does get refreshed)
- No new notifications show up on the app so I can’t approve access again
- /balance returns 200, so if that has 200 so should /transactions
I can fix the process by going over the authentication flow again but this is not suitable for my script which refreshes the access token every 12 hours. This was not erroring earlier in the year, but now my automation shows 403 errors for /transactions only while /balance still works just fine.
This feels like a bug. Can anyone help me understand how to avoid having to re-authenticate when 403s get returned?
thank you!