OAuth via Adobe IMS works, but Frame.io V4 API returns 401 (missing Frame.io authorization)

1

Hi Frame.io team,

I’m running into an authorization issue with the Frame.io V4 API that appears to be account / entitlement related, not an implementation problem.

Current state

  • OAuth 2.0 (Adobe IMS) Authorization Code flow works correctly

  • Access and refresh tokens are issued successfully

  • Tokens are valid and accepted by Adobe IMS

  • My Frame.io account is already connected to Adobe via the Frame.io web UI

  • Frame.io API is added to my Adobe Developer Console project

Problem

All Frame.io V4 API requests return:

401 Unauthorized
Invalid or missing authorization token

This happens consistently on endpoints such as:

  • GET /v4/me

  • GET /v4/accounts

  • GET /v4/workspaces

Token details

The issued access tokens contain only standard Adobe IMS scopes:

  • openid

  • offline_access

  • profile

  • email

  • additional_info.roles

There are no Frame.io-specific permissions, and the tokens are not accepted by the Frame.io V4 API, even though OAuth itself completes successfully.

What I’ve already verified

  • Redirect URI matches exactly (HTTPS)

  • OAuth flow works end-to-end

  • Scope formatting is correct (space-separated)

  • Frame.io ↔ Adobe account linking is complete

  • Issue persists across multiple tokens

Conclusion

This looks like a Frame.io V4 API entitlement / provisioning issue, where:

  • the OAuth client is allowed to authenticate via Adobe IMS

  • but is not authorized to access Frame.io V4 API resources

From my understanding, this cannot be resolved client-side or via the Adobe Developer Console alone.

Request

Could someone from the Frame.io team please confirm:

  • whether a specific Frame.io V4 API entitlement is required for existing accounts, and

  • whether this can be enabled for an existing organization, or if it is contract-bound

I’m happy to share any required identifiers (e.g. client ID) privately if needed.

Thanks in advance for taking a look.

Best regards
Moritz

2

Hi @mola you need to ensure that all of the scopes that are included in the developer console are present when you initially create the authentication request to IMS, as the auth token inherits those scopes when used for the Frame.io API (hence why there are no specific frame.io scopes).

Please double check to make sure you are properly adding the scopes based on the url formatting. You can find more information here: https://developer.adobe.com/developer-console/docs/guides/authentication/UserAuthentication/ims#authorize-request