# OAuth Token Working with Adobe IMS but Not Authorized for Frame.io API (401 Error) **URL:** \ **Category:** Uncategorized\ **Tags:** api\ **Created:** [August 26, 2025, 2:05pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806 "2025-08-26T14:05:14Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sgraham90](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@sgraham90](https://forum.frame.io/u/sgraham90)\ **Post date:** [August 26, 2025, 2:05pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/1 "2025-08-26T14:05:14Z")
We’ve implemented the OAuth flow using the Adobe Developer Console and are able to retrieve access tokens from [ims-na1.adobelogin.com](http://ims-na1.adobelogin.com). However, these tokens are not being accepted by the [Frame.io](http://Frame.io) API. **What’s Working** - OAuth 2.0 authorization flow is functional - Access tokens and refresh tokens are retrieved successfully - Web UI and admin dashboard are operational - Token refresh mechanism works as expected **The Issue** When using the token to call the [Frame.io](http://Frame.io) API (for example the “me” endpoint), the response is a 401 Unauthorized error. This suggests the token is valid with Adobe IMS but not authorized for [Frame.io](http://Frame.io). **OAuth App Configuration** - Authorization URL: [ims-na1.adobelogin.com/ims/authorize](http://ims-na1.adobelogin.com/ims/authorize) - Token URL: [ims-na1.adobelogin.com/ims/token](http://ims-na1.adobelogin.com/ims/token) - Scopes: offline\_access, openid, email, profile, additional\_info.roles - Redirect URI: [https://localhost/oauth/callback](https://localhost/oauth/callback) - Client type: OAuth Web App via Adobe Developer Console The scope “frame.io\_api” is not available when configuring the app, which may be the underlying cause. **Questions** 1. Does the Adobe Developer Console project need [Frame.io](http://Frame.io) to be explicitly added as an API or service? 2. What scopes are required to authorize [Frame.io](http://Frame.io) v4 API access? 3. Are there additional configuration steps or approvals required in Adobe Console for [Frame.io](http://Frame.io)? 4. If this OAuth flow is not the correct method, what is the recommended approach for authenticating with [Frame.io](http://Frame.io) v4? **Fallback** We have a fallback in place using the legacy v2 token-based API so the system continues to function, but the goal is to migrate to v4 for the improved features and security. **System Context** - OAuth managed through a web interface - Automatic token refresh for handling expiry - Upload system with retry logic for file sync - Admin dashboard with real-time monitoring Any guidance on the correct setup for [Frame.io](http://Frame.io) v4 OAuth integration would be greatly appreciated. ---
**Author:** ![RobertLoughlin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/robertloughlin/32/233_2.png) [@RobertLoughlin](https://forum.frame.io/u/RobertLoughlin)\ **Post date:** [August 26, 2025, 2:07pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/2 "2025-08-26T14:07:53Z")
Hi there! If the user is getting a 401 error, it sounds like the user needs to [link their Frame.io ID and Adobe ID](https://forum.frame.io/t/self-serve-adobe-authentication-connection/2667). This can be done in the [Frame.io](http://Frame.io) settings. There is no [Frame.io](http://Frame.io) specific scope required for the API keys, and you have all the required scopes selected. ---
**Author:** ![sgraham90](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@sgraham90](https://forum.frame.io/u/sgraham90)\ **Post date:** [August 26, 2025, 2:33pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/3 "2025-08-26T14:33:16Z")
Thanks for the suggestion. I did suspect that at first as well, but Frame support has already manually linked my Frame ID with my Adobe ID and confirmed the linkage, so I don’t think that’s the cause in this case. Even with the accounts linked, the OAuth tokens I’m receiving from Adobe IMS are still returning 401 Unauthorized when used against the Frame API. That’s why I was wondering if there’s something else required in the Adobe Developer Console configuration, or another step I might be missing to enable Frame API access on top of the standard IMS authentication. Happy to provide more detail on the exact responses or headers if that helps troubleshoot further. ---
**Author:** ![RobertLoughlin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/robertloughlin/32/233_2.png) [@RobertLoughlin](https://forum.frame.io/u/RobertLoughlin)\ **Post date:** [August 26, 2025, 2:53pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/4 "2025-08-26T14:53:23Z")
Got it. You’re testing the `/me` endpoint with the same user that has the IDs linked? This is a per-user requirement, not just for the owner of the app credentials. In addition, you _will_ need to make sure [Frame.io](http://Frame.io) is added as an API to the project. The new project flow in developer console should prompt you for the APIs you want to add when creating a project, but you can add these under the API tab when inspecting the project in the developer console. Another thing to check if you have [Frame.io](http://Frame.io) added is your redirect URI _pattern_. The pattern shouldn’t include the entire redirect address, just the root (ie, `https://localhost` instead of `https://localhost/oauth/callback`). ---
**Author:** ![CharlieAnderson](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/charlieanderson/32/491_2.png) [@CharlieAnderson](https://forum.frame.io/u/CharlieAnderson)\ **Post date:** [August 26, 2025, 7:58pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/5 "2025-08-26T19:58:10Z")
As Rob stated, 401 means you have no route to [Frame.io](http://Frame.io) from the Dev Console for that user. Be sure to check that the user logging in has infect connected their [Frame.io](http://Frame.io) account to an Adobe ID in the Frame settings. You’ll need to add the [Frame.io](http://Frame.io) V4 API to the project in order to get started. ![image](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/ac9829c915bf6fd952a2d90014631191fbfa4838.png) ![image](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/168503bd377452a8573ade7e65af6629af9511ed.jpeg) If you have the options below, choose User Authentication: ![Screenshot 2025-08-26 at 3.55.01 PM](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/af1dd7140ee5fb21f6034b4d06896d7de0cffc99.png) Then you’ll have to choose which credential type you’ll need for your integration ![Screenshot 2025-08-26 at 3.55.51 PM](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/432b18b5efe2962b0648824d9276173ea9c420bc.png) Then configure your redirect uri ![Screenshot 2025-08-26 at 3.56.26 PM](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/dc5830023625935098fb54c9499a973da2ebf2fc.png) Your scopes will be available to you on the next screen and also in the project details. You should see [Frame.io](http://Frame.io) API underneath the “Connected products and services” ![Screenshot 2025-08-26 at 3.57.35 PM](https://canada1.discourse-cdn.com/flex035/uploads/frame1/original/1X/cd0923208a1add9f2d6c003e9218748faee88012.png) ---
**Author:** ![sgraham90](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@sgraham90](https://forum.frame.io/u/sgraham90)\ **Post date:** [August 27, 2025, 12:59am UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/6 "2025-08-27T00:59:01Z")
Hi team, Thanks again for your help so far. We’ve successfully completed the OAuth v4 flow and can retrieve /me, /accounts, /workspaces, and /projects using the v4 API. However, we’re unable to access any child folders, list assets, or perform uploads using the v4 endpoints. Could you please clarify the current limitations of the v4 API? Specifically: 1. Are the following endpoints supported in v4 yet? • GET /v4/assets/{id} • GET /v4/assets/{id}/children • POST /v4/assets • POST /v4/accounts/{id}/workspaces/{id}/projects 2. If these are not yet available, is there an estimated timeline for when folder traversal and upload functionality will be added? 3. In the meantime, is there any supported way to access v2 endpoints using our current v4 OAuth tokens? Or do we need to set up a separate v2 integration for full asset and folder access? Our goal is to: • Read folder structures within projects • Upload video files programmatically • Create new folders and projects via the API Any guidance or recommended path forward would be greatly appreciated. Best regards, Sam Graham [sam@thecloudgeeks.co](mailto:sam@thecloudgeeks.co) ---
**Author:** ![CharlieAnderson](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/charlieanderson/32/491_2.png) [@CharlieAnderson](https://forum.frame.io/u/CharlieAnderson)\ **Post date:** [August 27, 2025, 4:10pm UTC](https://forum.frame.io/t/oauth-token-working-with-adobe-ims-but-not-authorized-for-frame-io-api-401-error/2806/7 "2025-08-27T16:10:15Z")
hi @sgraham90 all of the endpoints you asked about have been live since we launched the Early Access for our V4 APIs back in April. The endpoints you have listed are for our legacy API (read /v2) and are not translated directly, meaning you cannot just swap out /v2 for /v4 in your calls and have it work. You can find our V4 API references here: [https://developer.adobe.com/frameio/api/current/](https://developer.adobe.com/frameio/api/current/) We have a full migration guide from `/v2` to /`v4` on our documentation site to help with the transition: [https://developer.adobe.com/frameio/guides/Migration/](https://developer.adobe.com/frameio/guides/Migration/) > In the meantime, is there any supported way to access v2 endpoints using our current v4 OAuth tokens? Or do we need to set up a separate v2 integration for full asset and folder access? It is not possible to use /v2 endpoints with V4 accounts. If you are using Cursor/Claude/AI to parse our API reference, it’s inherently bad at doing so. I would recommend giving it our openapi spec to use as reference: [https://api.frame.io/v4/docs/4.0/openapi.json](https://api.frame.io/v4/docs/4.0/openapi.json) Please see our [Getting Started Guide](https://developer.adobe.com/frameio/guides/) for more info on how to get started with the V4 APIs.