Is it possible your user doesn’t have write permissions in the project you’re trying to create resources in? Or are you just not seeing the endpoints in the docs?
i’m using the endpoints from the docs, but I get this error when I try POST /v4/accounts/{account_id}/folders/{folder_id}/children
“no route found for POST /v4/accounts/…/folders/…/children (DeveloperApiWeb.V0.Router)”
/v4/accounts/{account_id}/folders/{folder_id}/children is the “List folder children” endpoint, it does not accept a POST hence why you are getting the “no route found”. If you are trying to create folders you need to use POST https://api.frame.io/v4/accounts/{account_id}/folders/{folder_id}/folders
thank you, working now
1 Like
how can we enable webhooks on an account? Or still in alpha?
Hi,
I represent a group of colorists, conformists, and editors who work as independent artists while using Mistika Workflows to automate their workflows. We have individual Adobe user accounts.
From what I have read so far, to communicate Mistika Workflows with Frame io V4, I need a “FRAME_IO_CLIENT_ID” and “FRAME_IO_CLIENT_SECRET”, which can only be obtained with an Adobe Enterprise account. This automatically excludes our entire group of creators from being able to use Frame io in our Mistika WF workflows 
Our programming and HTTP knowledge is quite basic, so perhaps you can suggest if there is any way, using Python, to communicate with the Frame io V4 API while having individual Adobe accounts? And/or possibly, are you planning to allow this in the near future?
Hi Tomasz!
What we call “server to server” authentication is limited to Enterprise accounts. Our non-Enterprise accounts use OAuth 2.0 for authentication. OAuth 2.0 still generates a Client_ID and a Client_Secret, but you would also need to manage the additional Refresh_Token. It’s been a long time since I’ve opened Mistika, so I can’t take a look at it to be able to tell you if this would work in WF. However, there are OAuth 2.0 libraries for Python that you might be able to use.
Ideally, Mistika could build a more integrated solution and handle the authentication for you – and users would only have to sign in using their Frame credentials instead of generating tokens themselves.
how can we enable webhooks on an account? Or still in alpha?
Webhooks are still in alpha for now, coming soon to stable!
@TomaszCzech to add to what @RobertLoughlin touched on, there are 3 different types of User Authentication as outlined in our documentation. I would assume Mistika would fall under the Native App, unless it is acting as a server on behalf of the user.
You only need to ensure your Frame.io account is connected to an Adobe ID as stated in the first post here to get access to the V4 APIs. If you require assistance, please dont hesitate to reach out to our support team to be able to assist you in linking your Frame.io account to an Adobe ID to gain access.
thanks, how can we sign up to access the alpha?
@WikRik the Alpha is available now, as per the reference documentation. Just make sure you are selecting the “Alpha Version” in the drop down to gain access to the alpha reference endpoints.
You will need to set the api-version:alpha in the header requests to ensure the routes go through, as per the Alpha Release Rules:
Alpha Release Rules
Alphareleases contain endpoints that may be still be in development and are subject to change.- Set the header
api-versiontoalphain order to access the alpha API.- It may be necessary to push breaking changes, so alpha is not suitable for integrations that run in production systems.
Hi @TomaszCzech, I meant to add this the other day and realized I forgot. In the Adobe documentation, they include some sample code for using OAuth 2.0 to authenticate to Adobe IMS (which Frame V4 uses) in Python. Hope this helps: https://developer.adobe.com/developer-console/docs/guides/authentication/UserAuthentication/implementation#standard-oauth2-libraries