I’m sure you get this question 1,000,000 times a day: is there a timeline for a V4 API? I have a wonderful workflow built between Airtable and Frame using the current API, but am also itching to dig into V4 and all it can do!
Thanks!
I’m sure you get this question 1,000,000 times a day: is there a timeline for a V4 API? I have a wonderful workflow built between Airtable and Frame using the current API, but am also itching to dig into V4 and all it can do!
Thanks!
+1 on this one, also have a lot of automations based on the API and after the upgrade this morning, everything is broken and not usable
We are just beginning to roll out support for our new developer API for V4! You can find documentation here, but access is currently limited to a subset of Frame.io enterprise accounts, managed through Adobe Admin console.
That is just a temporary limitation though and we are working hard to make the new V4 compatible developer platform available to everyone.
is there no temporary quick-fix we can use to still use our automations? they were a key part of our daily workflow so this is really disrupting things for us / making us look at other alternatives. Or at least any time estimate on how much longer it will be?
There’s definitely no “quick” fix that would unblock your automations right away unfortunately, they will all need to be updated to use a new authentication flows, new endpoints, new response models, etc.
Are your automations built using no-code tools like Make.com and Zapier, or are they more bespoke?
They’re on Make.com - mostly using it to upload files, but none of the end points work, not even getting the authenticated user
There is a no-code tool for uploading large files to frame that works with Make. Looks like it’s in beta but might be useful for what you are doing. https://fatfiles.webflow.io
The issue is with Frame.io though, regardless of the source of files there’s currently no API end points that work to upload stuff. The old V2 Endpoints no longer work and V4 API isn’t live yet. Thanks for sharing that though, looks cool
hey @jhodges, any update on this? We’ve got a huge system relying on this API. I can’t imagine you push people to upgrade to V4 and give no more option to downgrade, but at the same time limit access to the API which we used to have.
A timeline would be extremely appreciated. Thanks
We will have an update to share soon regarding a change in our policy for customers reliant on the API that were affected by a loss in functionality, and impacted automation workflows as a result of an update to V4.
We hear you, and we’re working on it!
Has there been any updates on this? It’s been almost a month since we last heard back on this. @jhodges
@bell @madisonleclef @Cameron @NanMelch2 Apologies for the delay on responding to you all, but if your transition from our Legacy platform to the new V4 has broken your workflows because of the lack of API support, please reach out to our support team (support@frame.io) via email or in-app citing such and they’ll help you resolve your issue. Again, apologies for the delay here!
Is there a way to convert back to v3? I’m having issues connecting with Strada. Please advise and thanks in advance. - Antonio
@ATarrell please reach out to our support team via the in-app chat or via support@frame.io and tell them you’d like to be rolled back to v3 because v4 doesn’t support an integration that’s important to your workflow and they’ll be able to help you out!
As a recent user of frame.io there is no way to get an account in the V3 version and support cannot give any ETA on the release of V4 API. The response I get is “While I don’t have an ETA for the release of the API I can say it’s actively being worked on.”
Not even whether this is matter of weeks, months, a year. This surprises me, how can we work from here?? Without any info I have to look for alternatives and will probably never switch back to frame. But it seems they don’t care.
@jhodges I tried to rebuild some of the automation that was working last year - I am following now your new documentation on Adobe Console but it tells me that I need license?
Somewhere else on Adobe forum I found that Frame. API is available only to Enterprise customers. I am on Pro.
So that means that you have effectively downgraded Pro plan and cut off access to API functionality?
Guys, it’s been months. Is there any way you can bring back the API? My whole agency is on manual mode because it’s not supported anymoree and got us tired…
At least give us a deadline please.
Hi all - for anyone that is frustrated by the unavailability of an API, but still want to automate things - just saying that almost all of the website is powered by GraphQL that you just can query directly once you have your authorization token. To get that:
r'window\.fioCSRFToken\s*=\s*"([^"]+)"'
x-csrf-token
authorization: Bearer
key from the response headers.@jhodges could you give some indications on what @takov mentioned here? this approach seems to work fine, but I can’t seem to find the way to specify the sourceURL of a video when uploading an asset to Frame.io with it, as when I do it from my browser and check the network tab, the Browser type is selected. This would be a big help if you could clarify with the team.
Thanks
What @takov shared is not supported officially in any way whatsoever, it is not a public API, and will not support uploads via source URL.
Please stay tuned a little longer for updates to our public-facing API eligibility!