POST
/
v1
/
run-chained-ffmpeg-commands
curl --request POST \
  --url https://api.rendi.dev/v1/run-chained-ffmpeg-commands \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --data '{
  "ffmpeg_chained_commands": [
    "-i {{in_1}} -i {{in_2}} -filter_complex '\''[0:v][1:v]hstack=inputs=2[v]'\'' -map '\''[v]'\'' {{inter_1}}",
    "-i {{inter_1}} -vf scale=1920:1080 {{out_1}}",
    "-i {{out_1}} -ss 00:17 -vframes 1 {{out_2}}"
  ],
  "input_files": {
    "in_1": "https://storage.rendi.dev/sample/first-video.avi",
    "in_2": "https://storage.rendi.dev/sample/second-video.avi"
  },
  "interim_files": {
    "inter_1": "concatenated_video.avi"
  },
  "output_files": {
    "out_1": "output_concatenated_1080.avi",
    "out_2": "thumbnail_1080.jpeg"
  }
}'
{
  "command_ids": [
    "123e4567-e89b-12d3-a456-426614174000",
    "987fcdeb-a89b-43d3-b456-789012345678"
  ]
}

Authorizations

​
X-API-KEY
string
header
required

API key required for authentication. Must be provided in the X-API-KEY header.

Body

application/json

Request model for submitting chained FFmpeg commands.

This model allows submitting multiple FFmpeg commands that run sequentially, where output files from earlier commands can be used as inputs to later commands. It supports both interim files (temporary) and output files (stored).

​
input_files
object
required

Dictionary mapping file aliases to their publicly accessible paths, file name should appear in the end of the url, keys must start with 'in_'. You can use public file urls, google drive, dropbox, rendi stored files, s3 stored files, etc. as long as they are publicly accessible.

Example:
{
  "in_1": "https://storage.rendi.dev/sample/first-video.avi",
  "in_2": "https://storage.rendi.dev/sample/second-video.avi"
}
​
output_files
object
required

Dictionary mapping file aliases to their desired output file names, keys must start with 'out_'. Output files can both be used as interm files as input for chained ffmpeg commands. Unlike interim files, output files will be stored in storage for later access.

Example:
{
  "out_1": "output_concatenated_1080.avi",
  "out_2": "thumbnail_1080.jpeg"
}
​
interim_files
object
required

These files are used for interm creation and processing between the ffmpeg chains. This is a dictionary mapping file aliases to their local paths, keys must start with 'inter_'

Example:
{ "inter_1": "concatenated_video.avi" }
​
ffmpeg_chained_commands
string[]
required

FFmpeg commands list of strings using {{alias}} placeholders for input, interim and output files. The interm files will only be stored on the local machine running FFMPEG

Example:
[
  "-i {{in_1}} -i {{in_2}} -filter_complex '[0:v][1:v]hstack=inputs=2[v]' -map '[v]' {{inter_1}}",
  "-i {{inter_1}} -vf scale=1920:1080 {{out_1}}",
  "-i {{out_1}} -ss 00:17 -vframes 1 {{out_2}}"
]

Response

200
application/json
Successful Response

Response model containing a list of command IDs returned from a batch command submission.

This model is used to return the unique identifiers for multiple FFmpeg commands that were submitted together. The command IDs are returned in the same order as the original command submission order.

​
command_ids
string[]
required

List of unique identifiers for the submitted FFmpeg commands, order by original commands order

Example:
[
  "123e4567-e89b-12d3-a456-426614174000",
  "987fcdeb-a89b-43d3-b456-789012345678"
]