The Frame.io API allows developers to integrate Frame.io’s surface for creatives and their teams to manage their work.
Go here to see the Frame V4 API reference pages.
Reach out to the Frame.io support team for assistance by chatting with us on our Support Site. Please note that enterprise customers may be directed to their Customer Success Manager.
Centralize, organize, and build all your end-to-end creative workflows at scale leveraging Metadata, Custom Fields, and Collections.
This set of capabilities gives users all the flexibility and power to build the best file management system for their creative process making it easier to quickly get the information they need, and manage all their work-in-progress assets at scale.
Frame.io helps creative teams reduce the total number of revision cycles with advanced review, commenting, and annotation capabilities available across a broad set of media types.
Customize and share creative work from one central place.
View and manage all users, workspaces, and projects in one place. Take bulk actions and export information to control how you utilize usage data.
A REST API documented via the OpenAPI 3.0 specification can connect Frame.io to the systems you already use to unlock custom workflows.
No. The Frame.io product released at Adobe MAX operates in fundamentally different ways and emphasizes different workflows than the legacy version. Due to these differences, the new API is not backward compatible.
Recognizing that backward-compatibility is a major concern for customers managing production-quality integrations with high uptime requirements, we are designing the V4 API to support an additional level of versioning via a custom HTTP header in order to allow clients to opt into using experimental endpoints, avoid breaking changes, and provide backward-compatibility guarantees within the /v4 API namespace.
All automations using legacy developer tokens will no longer work for V4 accounts. We do not have any way to migrate them to V4.
The V4 API is currently available for new Enterprise customers and select customers and partners via testing accounts.
We do not yet have any Collections endpoints publicly available. But, Collections management is under development.
URLs returned in media_links includes (such as download_url, inline_url, and url) are temporary signed URLs — they expire and cannot be reused indefinitely.
In practice, expiry is aligned to UTC noon or midnight, so the actual time remaining when you receive a URL may be anywhere between a few minutes and 24 hours depending on when the request is made.
Do not store or cache these URLs. Always request a fresh set of media_links each time you need to serve or access a file. Attempting to use an expired URL will result in a 403 error from the CDN.
The existing Zapier integration however does not work with V4 yet but it is in development.
No, not yet but it is in development.