Camera To Cloud
The Camera to Cloud API provides a straightforward authentication protocol designed for devices with limited display capabilities. Once authenticated, your device can upload on-set data directly to the cloud. The system supports most standard file formats for video, audio, LUT/CDL, and timecode data. For more details about C2C Certified Connections, visit our information page.
Getting Started
Sign up on our developer site and we'll contact you to guide you through the Cloud Devices integration process.
After reviewing your device, we'll set up a shared Slack channel and work with you to create an integration plan and timeline. You'll receive a development package with all the materials needed to build a successful integration.
Documentation Resources
This article is the first in a series of guides to help with your C2C integration. These guides are starting points—we encourage you to reach out to our team with questions or suggestions for improving the documentation or API. Think of these as foundations for your integration journey, not comprehensive references.
Developer Package
Your development package will include:
1. Client Secret
Frame.io will create a configuration model in our backend for your device. Once completed, you'll receive a client_secret for your device, commonly called a device model identifier.
2. Reference Implementation
You'll receive a Python reference implementation with skeleton code that emulates hardware devices through a CLI tool. This includes commented code and documentation outlining key integration steps.
3. Validation Process
Before launch, you'll participate in a quality assurance process with Frame.io engineers to ensure your device performs as expected. Our goal is to help all integrators achieve consistent quality standards for end-users working with your cloud-connected device. This provides valuable feedback before public release. We'll provide a checklist of review items, but you can also refer to our C2C Integration Checklist to understand what makes a successful integration.
4. Support Materials
You'll receive materials to help your team understand Frame.io's value proposition, demonstration techniques, and access to a dedicated Slack channel for working with our team. If you need additional support—such as a Frame.io platform demo or integration best practices workshop—let us know, and we'll arrange appropriate sessions.
Planning Your Integration
Before or during your conversations with our team, several technical details will need to be addressed. You don't need to have all this information ready before contacting us—this overview is to help you start thinking about these aspects.
Device Information
We'll need some basic information about your device:
- The exact name of your device
- A logo in SVG format, preferably monochromatic
Authentication Method
We now exclusively support the 6-digit code authentication flow. For applications, we offer an enhanced method using a special header parameter when requesting a device code to enable our URL pairing flow. This returns verification_uri_complete or verification_uri parameters you can use to generate a URL via hyperlink or a QR code for users to tap or scan. This starts a streamlined pairing process that connects directly to the user's selected project. For implementation details, see the Enabling QR Code Pairing Guide.
Marketing Collaboration
Each new Cloud Devices integration offers innovative solutions to creative workflow challenges. We appreciate the significant investment required to develop and launch your integration.
To support adoption, we'll work with you to create resources for our customers and the broader market. While marketing approaches are tailored to each integration, typical activities include:
- Working with our Solutions team to design and document optimal use cases and workflows
- Collaborating with mutual clients to develop case studies showing your integration in production
- Creating sales materials for our team to connect users with your device and workflow solutions