API access returning 404/Permission Denied on Adobe-migrated account

1

Was sent here by your support desk !

Hi support,

We’re building an internal creative review dashboard that needs to pull video thumbnails via the API. Our account was migrated to Adobe infrastructure (from_adobe: true on our user profile).

What’s happening:

Our Developer Token (fio-u-…) successfully authenticates against GET /v2/me and returns our user profile (account ID: a4ce***********af4, user: hello@bu###.com)
However, ALL asset/project/folder endpoints return 404 Not Found on REST v2
GraphQL queries for assets return PERMISSION_DENIED
This includes projects and assets we can access fine in the web UI

What we need:

REST v2 GET /v2/assets/{asset_id} to return asset details including thumbnail URLs
Or GraphQL asset(assetId: “…”) queries to work
Specifically, we need thumb_256 / thumb_540 fields from video assets for display in our dashboard

Our project/folder IDs (accessible in web UI but not via API):

Project: b5df2802
Folder : all

Questions:

After Adobe migration, do Developer Tokens need to be regenerated with specific scopes?
Is there a different auth flow required for Adobe-migrated accounts (e.g. Adobe IMS tokens)?
Are there any workspace/team-level permissions that need to be enabled for API access?

Our Developer Token was generated from the developer portal. We also have OAuth client credentials configured (client_id: 2b72************************************6259) but the access token returns 401.

Thanks,

2

hi @Bunnie looks like your account is a V4 account which means any /v2 API calls will not work, they are not compatible with V4.

Developer tokens generated at developer.frame.io do not work with V4 unless under very certain conditions at this time. You need to use the specific header outlined in our documentation here in order for it to work: https://next.developer.frame.io/platform/v4/docs/guides/authentication/python-sdk#legacy-developer-tokens

If it does not work for you then you do not meet the conditions and therefore must use OAuth via IMS to create an integration into Frame.io (OAuth apps created via developer.frame.io will not work). You can find more information about authentication here and how to get started here.

If you are using LLMs for your project, you can use our llms-full.txt which will give the entire context of our dev docs to the LLM to pull from.

Also I would highly recommend you use our Python SDK for Auth (Typscript Auth is coming soon) as it handles all the diifficult logic for you automatically.