The Frame.io legacy API is being deprecated and will no longer be supported after December 1, 2026. After that date, V2 API endpoints will be removed. Many developers have already moved over to V4, but for those who haven’t, that is the deadline to do so. (Note: this does not apply to C2C integrations.)
Instead of having multiple threads about the migration, we thought it might be helpful to create a single place to ask questions, share feedback, and get help throughout the process. We understand that changes like this can come with questions and require updates to your integrations, and we want to be as available (and helpful!) as possible between now and then.
If you haven’t seen it already, our Migration Guide was recently updated based on developer feedback. It breaks down major changes in a comprehensive, yet easy to follow format: Migration | Frame.io API Documentation
Here is the checklist outlined in the guide, so you can see at a glance what moving over entails:
Migration Checklist
1. Authentication
Some V4-migrated accounts not yet administered via the Adobe Admin Console can continue to use Legacy Developer tokens managed in the legacy Frame.io developer site, but will need to add a new header to API requests with the key x-frameio-legacy-token-auth and a value of true. Otherwise the Authentication section of the Migration Guide details how to switch over from legacy tokens to OAuth 2.0.
2. Update Existing API Calls
All legacy API routes will need to be mapped to the new V4 API routes and JSON payloads. There is a fairly comprehensive mapping table in the Migration Guide to assist with this process.
3. Testing Is Highly Recommended
Test thoroughly. Because there are many changes to the API, it is recommended to test with a V4 account to ensure that the new API is working as expected.
4. Implement Dedicated Login
Implement a dedicated login method for V4 due to separate Auth URLs. The V4 Auth URL is different than the Legacy API, and it will not return accounts not yet upgraded to V4 in the response and should be treated as a separate integration.
From conversations with teams that have already moved over (or are currently planning their migration), authentication and endpoint mapping are the things that come up the most. The mapping table from the Migration Guide is linked above, which should address the latter.
For authentication, it’s worth noting that both the V4 Python and TypeScript SDKs have their own auth modules with OAuth 2.0 support built in:
- Python SDK Auth Guide - Python SDK | Frame.io API Documentation
- TypeScript SDK Auth Guide - Typescript SDK | Frame.io API Documentation
I’ve also tagged all relevant posts on the forum with v4-migration so you can easily find questions that came in before this post was created. If you do find a previous discussion that relates to your migration, feel free to continue the conversation in this thread.
And finally, if questions come up in conversations off the forum, we’ll make sure they get added and answered here. The goal is to make this thread the central place for V4 migration support.