V4 API returns 403 Forbidden on all endpoints despite valid Adobe IMS OAuth token

Help
1

We set up a Frame.io V4 API integration via Adobe Developer Console (OAuth Web App). Adobe IMS authentication works — we get a valid access token. But every V4 endpoint returns 403.

Setup:

  • Scopes: openid, profile, email, offline_access, additional_info.roles

What works:

  • GET /v2/me → 200 :white_check_mark: (returns user info)

  • Adobe IMS token exchange → valid JWT :white_check_mark:

What fails (all 403):

  • GET /v4/me

  • GET /v4/accounts

  • GET /v4/accounts/{id}/workspaces

The token is a valid Adobe IMS JWT. The /v2/me endpoint confirms the token is accepted. But all /v4/* routes return a plain 403 Forbidden HTML page (not a JSON error).

Is there an account-level provisioning step required for V4 API access? Or are we missing a scope?

2

hi @attget can you remove email from the scopes and see if that works for you?

Also /v2 & /v4 are not compatible. The token created by IMS should not work for /v2/me if it does then something is not working correctly.

Also, would recommend you use the Python Auth SDK to see if that would work for you as well.

1 Like