The destinations feature lets you send rendered assets, ingested footage and renditions to built in and 3rd party services directly from the API. Once integrated videos and images will automatically be distributed to the destinations you specify.
Most destinations require you to add credentials, keys or passwords. These can be added via the dashboard from the integrations page. Each destination includes integration instructions and form fields to enter credentials and any other configuration options.
Example integrations page for the Mux destination:
You instruct a render or ingest task to send output files to a destination using the
destinations parameter. When
editing videos you set the destinations parameter in the
output, and for ingested source files and renditions you set
the value at the root level of the request body.
destinations parameter is an array of one or more destinations to send assets to. You can send one asset to
An edit output configuration to send a video to the Mux destination might look like:
Using the ingest API to send a source file to the Mux destination might look like:
The Serve API lets you check the status of asset transfers and their availability at each destination.