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