Request device code
Headers
x-client-version
Firmware or software version of a C2C integration. Will be used to determine the correct Device Model configuration for the device when multiple are available. Must be a valid semantic version.
For more on semantic versions, see here: https://semver.org/
x-client-platypus-enabled
Enable URL Pairing mode for C2C device code requests. Set to 'true' to enable.
Allowed values:
Request
client_id
A unique identifier for the physical hardware device. This value needs to be guaranteed to be unique for the device. This could be a serial number or a randomly generated UUID.
client_secret
This will be issued to you by Frame.io support and identifies the your device model. This value should be kept secret from the user, and should be encrypted at rest
scope
Space-delimited list of permissions being requested. Hardware devices can request the following scopes: ‘asset_create’ (create assets), ‘offline’ (refresh tokens). Typically both are requested together.
Response
Successful request
device_code
The device code should be hidden from the user, and is used to identify this authorization request when polling to see if the user has entered their code successfully.
expires_in
The number of seconds until this code expires.
interval
How long the we should wait between polling requests to see if the user has entered the code.
name
The name of the device we are trying to connect.
user_code
The six-digit code the user will enter into Frame.io to pair the device to a project.
verification_uri
The URL where the user should go to enter the pairing code.
verification_uri_complete
A complete URL with the user code pre-filled, which can be used to streamline the pairing process.