Introducing the Frame.io V4 API Early Access Program

General
1

Hi everyone, thank you all for being so patient while we have been working tirelessly behind the scenes. We have heard your frustrations and have taken your feedback seriously about getting access to the V4 APIs ASAP. Due to the nature of re-writing the entirety of Frame.io from the ground up for V4, we were also forced to re-write all the API endpoints in the same manner. Regardless, this took longer than we anticipated. However, we’re excited to announce Early Access to the Frame.io V4 API for everyone, regardless of your account type, starting today. We’re looking forward to hearing your feedback as we continue development of our V4 API on a regular basis.

With this early access to Frame.io V4 APIs, anyone can explore our developer documentation and integrate their solutions without requiring Adobe Admin Console access. This marks a major step toward expanding API eligibility while we continue development on provisioning and managing Frame.io accounts through Adobe identity systems.

Because this access is being provided during active development, there are a few important considerations:

  • Users must have their Frame.io account linked to an Adobe ID to be able to access V4 API functionality as an end user. If you do not see the Adobe SUSI screen when logging into your Frame.io account, please reach out to our Sr. Developer Relations, Partnerships team member Jeff Hodges to directly help with requests -jhodges@adobe.com.
  • Users must create a project in the Adobe Developer Console and then add Frame.io as a product to gain access to the V4 APIs.
  • Currently, there are two versions of the API: a Current Version, and an Alpha version which can and will be updated regularly to introduce new features and functionality. If you intend to use any endpoints from the Alpha version for your integration, please be aware that your integration may experience issues as we make changes. Please keep a keen eye on and awareness of our developer guides for more information as this evolves.
  • In the future, we will migrate all Frame users to the Adobe Admin Console. This will not break existing customer API workflows, but it will change how you can access multiple accounts. This transition is necessary to introduce interoperability across all Adobe products (such as AEM, Firefly, etc.) and so we can enable Server to Server (S2S) authentication. Once a customer’s account is on Adobe Admin Console, they can create a new project so everyone in the account has visibility into the active APIs.
  • All current V3 integrators will need to update their endpoints to include V4 endpoints in order to work with Frame.io V4. We recommend having a login specifically for V4 and treating it like a different integration entirely. Until then, users who upgrade to V4 will not have access to 3rd-party integrations. Please see our V3->V4 Migration Guide to see which endpoints you need to adjust.
  • At this time, Webhooks are only available via the Alpha version of the API. They will soon be moving to the Stable version with more features, such as including Event IDs and filtering at the different resource levels (Account, Workspace, Project).

If you’re eager to start building with the V4 API, you can get started today! Please see our getting started guide and FAQs to begin your API journey!

We’d love to hear your feedback as you explore the new V4 API capabilities—let us know your thoughts in the comments below!

-Charlie

2 Likes
2

Great news!! Christmas is early this year.

If anybody here can help me with setting up some automation in Frame pls dm me.

  • Frame → G-drive
  • Frame → Dropbox
  • Frame → YouTube
1 Like
6

Hi Charlie,

Good to see the v4 API is progressing. We are looking forward to begin testing our multiple integrations with v4…
However, We are currently running those multiple critical integrations/automations on the v2 API (Frame io v3)… We absolutely CANNOT mess with those integrations (we already had to get rolled back to v3 when v4 first launched and the API world of Frame io went haywire)

So, our thought was to purchase a 3rd “team” license as Frame io v4 … While keeping our current two Frame io licenses as v3

So, the confirmation we are looking for is… Can we purchase a 3rd license as v4 and keep our other 2 licenses as v3 with ZERO conflicts with our v2 API integrations while testing that 3rd v4 versions v4 api?

Thanks
C

7

Hi @CM1776 you could sign up for a free trial with a new email account (during the sign up process be sure to click “sign up with Adobe”) and use that to explore your integration with the V4 API. Even if the free trial lapses and you move to a free account (with 2GB of storage) you will still be able to access the V4 API. Since the V4 APIs are a completely new rewrite and design, your current V2 integrrations will not be affected. We currently recommend you have 2 separate logins, one for Frame.io Legacy & Frame.io V4, so that you can direct your users to the proper auth flow as they are completely different URLs and functionality. Please don’t hesitate to reach out if you have any questions.

8

For your existing integrations, can you share some more details?

Do you use webhooks, Custom Actions, or developer tokens?

Are there 3rd party integrations you use?

9

Hi Charlie,

Thanks for the reply and info. That was good news. I think we will likely jump right into a free V4 account or even an additional team account. and register it with a different account within the company.
Looking forward to beginning testing with the new API and frame v4.

Thanks again
C