Frame.io V4 API – OAuth Token from Adobe IMS Not Authorized (401 on all V4 endpoints)

Help
, ,
1

Hello,

I am experiencing an authentication issue when using the Frame io V4 API through Adobe IMS, despite having a fully configured project in the Adobe Developer Console.

Technical Context

My Adobe Developer project is configured with:

OAuth Web App (Authorization Code + Refresh Token)

  • client_id: d021c3cb3dee49c3b559ff06f1073f09

  • redirect_uri: h ttps://localhost

  • scopes: openid, offline_access, email, profile

  • Connected Adobe user:

  • The Frame io API is added to the project.

The OAuth flow works correctly:

I receive an authorization code

  • I exchange it via /ims/token/v3

  • I receive a valid access_token and refresh_token

  • Refreshing the token also works as expected

What Works

GET h ttps://api.frame.io/v2/me
Authorization: Bearer <access_token>

I correctly receive 200 OK, proving that my IMS access token is valid.

:cross_mark: What Fails

All Frame io V4 endpoints return 401 Unauthorized.

Example:

GET h ttps://api.frame.io/v4/accounts

Response:

{
“errors”: [
{
“title”: “Unauthorized”,
“detail”: “Invalid or missing authorization token”
}
]
}

The same error occurs on file creation:

POST /v4/accounts/{account_id}/folders/{folder_id}/files

With headers:

Authorization: Bearer <access_token>
x-api-key: <client_id>
Accept: application/json

:puzzle_piece: Likely Cause

It appears that the IMS access_token does not include Frame io V4 product entitlements, even though:

  • The Frame io API is added in Developer Console

  • The Adobe user is authenticated properly

  • The refresh token is valid

This suggests that my Adobe organization (Eurodes) may not be assigned a Frameio V4 product profile, or the Developer project is not linked to it.

When this association is missing, Frame io V4 rejects the token with 401, even though IMS validates it.

:folded_hands: What I Need You to Verify

Could you please check:

  1. Whether the Eurodes organization has an active Frame io V4 product profile.
  2. Whether freddy.——-@ is assigned to this product profile.
  3. Whether my Developer Console project (client_id provided above) is authorized to access the Frame io V4 API.
  4. Whether the IMS token generated for this user contains the necessary claims / entitlements for Frame io V4.

Without proper product association, all V4 endpoints reject the IMS token with 401 Unauthorized.

Thank you very much for your help,

Kind regards,

Freddy

New Frame.io Developer Site + V4 API Updates
2

Hi @freddy looks like you are missing scopes. You should have:
offline_access, openid, email, profile, additional_info.roles

Also please make sure you have an adobe id connected to your frame.io account.
Please see Connecting to Adobe authentication | Frame.io V4 Knowledge Center

3

Hi Charlie,

I wanted to thank you for your input and for pointing me in the right direction.

Your technical insights — especially regarding how uploads and endpoints work in Frame.io’s v4 system — were extremely valuable. It saved me a lot of trial and error, and helped me move forward with my sync script confidently.

I really appreciate the time you took to help.

Thanks again for your support and expertise!

Warm regards,

Freddy