We’ve implemented the OAuth flow using the Adobe Developer Console and are able to retrieve access tokens from ims-na1.adobelogin.com. However, these tokens are not being accepted by the 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 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.
OAuth App Configuration
The scope “frame.io_api” is not available when configuring the app, which may be the underlying cause.
Questions
-
Does the Adobe Developer Console project need Frame.io to be explicitly added as an API or service?
-
What scopes are required to authorize Frame.io v4 API access?
-
Are there additional configuration steps or approvals required in Adobe Console for Frame.io?
-
If this OAuth flow is not the correct method, what is the recommended approach for authenticating with 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 v4 OAuth integration would be greatly appreciated.
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. This can be done in the Frame.io settings.
There is no Frame.io specific scope required for the API keys, and you have all the required scopes selected.
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.
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 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 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).
As Rob stated, 401 means you have no route to Frame.io from the Dev Console for that user. Be sure to check that the user logging in has infect connected their Frame.io account to an Adobe ID in the Frame settings.
You’ll need to add the Frame.io V4 API to the project in order to get started.
If you have the options below, choose User Authentication:
Then you’ll have to choose which credential type you’ll need for your integration
Then configure your redirect uri
Your scopes will be available to you on the next screen and also in the project details.
You should see Frame.io API underneath the “Connected products and services”
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:
- 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
- If these are not yet available, is there an estimated timeline for when folder traversal and upload functionality will be added?
- 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
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/
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/
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
Please see our Getting Started Guide for more info on how to get started with the V4 APIs.
