I’m building an integration using a legacy developer token from developer.frame.io, with the documented x-frameio-legacy-token-auth: true header included on every request.
GET /v4/me → works correctly (200, returns my account info)
GET /v4/accounts → returns 403 Forbidden: {"errors":[{"detail":"Forbidden"}]}
This happens even with a freshly generated token with all read scopes enabled.
Could someone check whether my account needs to be linked/enabled for V4 API account-level access? I found other posts here with this exact same symptom (works on /me, 403s on /accounts), which suggests a backend account-linking issue rather than something wrong on my end.
Sorry to hear you’re running into trouble here. If you haven’t connected your Frame and Adobe accounts, you can find instructions on how to do so here:
Just a heads up, I edited your post to remove your email address. As for the 403 you’re seeing, this may be related to using a legacy developer token. You can confirm this by making an API request via the console in our docs:
From that page, hit ‘Login’ (make sure to use the account you’ve been testing with), then ‘Send request’. The console authenticates with an OAuth access token rather than a legacy developer token. If the request is successful there, that points to the developer token being the source of the error.
If that’s the case, you’ll need to authenticate using OAuth. You can find more information on V4 authentication here:
I hope this helps! If you continue to run into this error, please let us know and we’ll be happy to look into this further.
Hi again — following up with more context that I think explains the issue.
I previously linked this Frame.io account to Adobe identity, but had to ask your support team to revert it, because Adobe-linked accounts require individual logins and my team shares one Frame.io account across multiple editors (we can’t have everyone on separate paid seats).
Given that, OAuth isn’t a usable option for us — we specifically need the legacy developer token to work, since it’s the only method that doesn’t require individual Adobe identities per user.
My suspicion is that the revert wasn’t fully completed on your end, and my account is stuck in a partial state — which would explain why GET /v4/me works fine but GET /v4/accounts returns 403 Forbidden even with a fresh token and full scopes.
Could someone check whether my account has any leftover Adobe-linkage from that earlier attempt, and fully clear it so legacy developer tokens work as intended?