Authorization
header. Make sure you have your API key ready. You can find it in your dashboard and it should look something like this:url
where the video is stored, or try out our asset
service to upload and store the video yourself. (This walkthrough will show you how to render video via a public url
but you can also check out our creating an asset guide for more info on the assets feature)elements
array. We'll start off with the source video shown above. When making the request, change the source.url
string to match the location of the video you are planning to use:source.url
it is possible to provide source.asset_id
and use a video uploaded to our service previously. Find out more at creating an asset​crop
object, as a member of the video element params
. The following picture shows how the crop
object acts on the video element:trim
object to the video elements params
. (Note that trim values are in seconds)text
element to our elements
array.param
is value
(the string of text you want to include), but we will also provide a position
object, to place it using alignment string enums. You can, of course, use precise pixel values if you wish.render.json
file. Then, from the directory where the file is saved, run the curl
command with the file name as a POST body. Make sure to change the API key to match the one from your dashboard:id
represents the task that is in charge of rendering. The id
is used to track the progress of the render and get the final result.id
returned:QUEUED
, PROGRESS
,SUCCESS
,FAILED
PROGRESS
, which will look like this:payload
object you will get a progress
field, which indicates the percentage of rendering complete. Once it reaches 100 your render is done, and you need to poll the API once more:SUCCESS
response.url
you can download the resulting render and enjoy your new video!