New Frame.io Developer Site + V4 API Updates

General
,
1

Hey everyone, Rosie here :waving_hand:

I’m the new Developer Relations Engineer on the Frame.io Partnerships team. You’ll be seeing me around here more, so if you have questions, run into a problem, or want to talk about what you’re building, feel free to tag me.

Aside from saying hello, I’m also here with an update. We’ve launched a new developer site for the Frame.io APIs (V4, Legacy, and C2C) and I wanted to give you a closer look at what’s new:

  • An updated API Reference with examples in Python, TypeScript, Java, C#, and more
    (cURL is still there if that’s your preference, but now you have a lot more options)
  • Python and TypeScript SDKs built for V4
  • AI-powered search trained on our documentation
  • A Try It console you can use to make live API calls directly from the docs with your own credentials. (I should note that your account ID won’t be pre-populated, and you’ll need it for most endpoints. Hit /v4/accounts first to grab it)

A quick update on the V4 API as well. We’ve promoted the following endpoints from experimental to stable:

Files
/v4/accounts/{account_id}/files/{file_id}
/v4/accounts/{account_id}/files/{file_id}/copy
/v4/accounts/{account_id}/files/{file_id}/move
/v4/accounts/{account_id}/files/{file_id}/status
/v4/accounts/{account_id}/folders/{folder_id}/files/remote_upload

Folders
/v4/accounts/{account_id}/folders/{folder_id}/copy
/v4/accounts/{account_id}/folders/{folder_id}/children
/v4/accounts/{account_id}/folders/{folder_id}/move

Version Stacks
/v4/accounts/{account_id}/version_stacks/{version_stack_id}/copy
/v4/accounts/{account_id}/version_stacks/{version_stack_id}/children
/v4/accounts/{account_id}/version_stacks/{version_stack_id}/move
/v4/accounts/{account_id}/folders/{folder_id}/version_stacks

Metadata
/v4/accounts/{account_id}/metadata/field_definitions
/v4/accounts/{account_id}/metadata/field_definitions/{field_definition_id}
/v4/accounts/{account_id}/files/{file_id}/metadata
/v4/accounts/{account_id}/projects/{project_id}/metadata/values

You can check it all out here: https://next.developer.frame.io/

We’re still refining the site based on feedback, so if something feels off or slows you down, use the “Was this helpful?” link at the bottom of the page. Those messages go directly to our team.

If you’ve been building with the API or SDKs, or experimenting with integrations and no-code workflows, feel free to share! Always curious to see what people are working on.

2 Likes
2

Hi @rosiec,

I’m integrating with the Frame io V4 API using Adobe IMS OAuth (Web App flow).

Authentication with Adobe works perfectly:

  • I get a valid authorization code

  • I exchange it at ims/token/v3 and receive access_token + refresh_token

  • Token refresh also works

  • The endpoint /v2/me returns 200 OK

But every V4 endpoint returns:

401 Unauthorized – “Invalid or missing authorization token”

Examples:

GET https://api.frame.io/v4/accounts

POST https://api.frame.io/v4/accounts/%7Baccount_id%7D/folders/%7Bfolder_id%7D/files

I am sending the correct headers:

Authorization: Bearer <access_token>

x-api-key: <client_id>

Accept: application/json

Additional observations:

  • The endpoint /v2/accounts returns an empty list, which indicates that my Adobe identity is not linked to a Frame io V4 account.

  • Zapier can successfully list my Projects, Workspaces, Folders and Files, so the V4 account exists and permissions are valid.

  • The Frame io API is correctly added to my Adobe project.

This strongly suggests the issue is related to Identity Linking or missing product entitlements.

Could you please confirm:

  1. That the user ……@……. is correctly linked to the Frame io V4 identity.

  2. That my Adobe organization “Eurodes” has an active Frame io V4 product profile.

  3. That my Adobe Developer project (client_id: d021c3cb3dee49c3b559ff06f1073f09) is authorized to request V4 tokens containing Frame io entitlements.

Happy to provide additional logs, request examples or tokens if needed.

Thanks again for your help!

Best regards,

Freddy

3

Hi @freddy

It looks like Charlie responded before I was able to over here: Frame.io V4 API – OAuth Token from Adobe IMS Not Authorized (401 on all V4 endpoints)

but to reiterate: make sure you’re including these scopes in your request to ims/authorize/v2:

offline_access, openid, email, profile, additional_info.roles

Also please make sure you have an adobe id connected to your frame.io account.
Please see Connecting to Adobe authentication | Frame.io V4 Knowledge Center

Hope this helps!

4

Hi Rosiec,

Thank you so much for taking the time to explain things so clearly.

Your guidance really helped me understand the logic behind the Frame.io API workflow and the authentication steps. I had been stuck for quite some time, and your explanation finally connected all the dots.

I truly appreciate your patience and the level of detail you provided — it made a real difference.

Thanks again for sharing your expertise so generously!

Best regards,

Freddy

5

Thanks for this. FYI, the reference link on the Python SDK pypi page seems to be wrong/broken:

https://github.com/Frameio/python-sdk/blob/HEAD/reference.md

6

Thanks for letting me know @hc-evan! It looks like this repo is set to private. Let me see what public resources we can link to instead. I’ll update here shortly.