Our Cloud Devices API combines a simple authentication protocol with an easy-to-follow user experience, and supports devices with limited screen display options. Once authenticated, your device can upload on-set data directly to the cloud. Most standard file formats for video, audio, LUT/CDL, and timecode data are supported. Check out our C2C Certified Connections info page!
Sign up on our developer site and we will reach out to walk you through the Cloud Devices integration process.
After evaluating your device, we will setup a shared Slack channel and collaborate with you on an integration plan and timeline. In addition, we will provide you with a development package containing the requisite materials for you to build a successful integration.
This article is followed by a number of guides to help you through your C2C integration. Don’t feel that these are the only place to look for help! As you are following along, please ask our team questions if you get stuck or have suggestions on how to improve the guides or API. They are there as a starting point for your journey, not the destination!
The bundle we will provide to your development team will contain the following:
1. Client Secret / Client ID
For each viable device or application, Frame.io will create a configuration model on our backend. Once complete, we will send you a
client_id to your device (see the section on integration types below), commonly referred to as a device model identifier.
2. Reference Implementation
We will provide a reference implementation in Python with skeleton code for emulating hardware devices via a CLI tool. We will provide commented code and a detailed README to outline key integration steps.
3. Validation Checklist
Prior to launching your integration, we will invite you to collaborate in a quality assurance process alongside Frame.io engineers to ensure your device behaves as expected. Our aim is to help all integrators achieve a consistent high bar for end-users who will use your cloud connected device on set.
Either before or after you reach out, there are some things we’ll need to work together on to get your integration up and running. Don’t feel you have to have this information ironed out before reaching out to us! We are simply putting it here to give you a head start on your integration.
First we’ll need some information about your device! Here is a list of what we will need to glean from you:
- The name of your device
- A logo for the device
- How each of your devices will uniquely identify itself
There are two ways to integrate with the C2C API: as a Hardware Device or as a C2C Application. This choice determines how your device authenticates and authorizes with Frame.io.
We can talk through this choice more deeply with you. If you wish to do a deeper dive on your own, you glance over the Integration Architecture guide, and the hardware and C2C Application authorization guides — authorization is what differentiates the two types of devices.
Each new Cloud Devices integration will provide new, inventive solutions to creative workflow challenges. Beyond the workflow, however, we truly value the time work you'll put into bringing a unique solution into the world.
To help support adoption, we will work with you to create resources for our customers, and the market at large. While we will always work to create a marketing offering that best fits each integration, typical steps include:
- Working with our Solutions team to design and communicate best-practice use cases and workflows.
- Collaborating with our mutual users to create compelling case studies of your integration in action.
- Building sales collateral and enablement materials for our sales team to drive users to your device and workflow.
If you haven’t already, we encourage you to reach out to our team, then continue to the next guide. We look forward to hearing from you!