V4 OAuth works with Adobe IMS, but Frame.io API still returns 401

Help
1

Hi, wonder if anyone can help…

I’m trying to migrate from the legacy v2 API to v4 and hitting a consistent 401.

What’s working

  • OAuth 2.0 flow via Adobe IMS works

  • User successfully authorises (browser flow)

  • Access + refresh tokens are issued

  • Token decodes with scopes: openid profile email offline_access additional_info.roles

  • Frame. API is added to the Adobe Developer Console project

  • Frame + Adobe ID are confirmed linked (Frame support verified)

What’s failing

  • Any call to the Frame.io v4 API (including /me) returns:
    401 Unauthorized – Invalid or missing authorization token

Details

  • Auth: OAuth Web App (User Authentication)

  • Token source: https://ims-na1.adobelogin.com

  • Using Authorization: Bearer <access_token>

  • Redirect URI is a Google Apps Script web app (/exec)

  • This works fine with v2 tokens, but v4 always fails

Question
Is there anything else required to make an Adobe IMS token valid for Frame v4 (project config, scopes, account flags, redirect URI pattern rules, etc.), or a known gotcha that still causes 401s even when everything appears correctly linked?

ta

Ben

2

Anyone can help with this? I tried Frame support but they said to post on. here so I’m completely stuck otherwise…

3

hi @Ben1 Invalid or missing authorization token typically means you are missing some scopes on calls or you are using the wrong path for auth/token refresh.

Can you post some of your auth code here for us to take a look at? You can DM me if you’d like to keep it more private.

It should be something along the lines of:

https://ims-na1.adobelogin.com/ims/authorize/v2
  ?client_id={CLIENT_ID}
  &redirect_uri={REDIRECT_URI}
  &scope={SCOPES}
  &state={STATE}
  &response_type=code

Just FYI the IMS endpoints are https://ims-na1.adobelogin.com/ims/authorize/v2& https://ims-na1.adobelogin.com/ims/token/v3 as per the IMS docs.