POST
/
v1
/
run-ffmpeg-command
curl --request POST \
  --url https://api.rendi.dev/v1/run-ffmpeg-command \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --data '{
  "ffmpeg_command": "-i {{in_1}} -ss 00:00 -to 01:00 -vf select='\''lte(n\\,1)+gt(trunc(t/10),trunc(prev_t/10))'\'',setpts='\''PTS*0.025'\'',scale=trunc(oh*a/2)*2:160:force_original_aspect_ratio=decrease,pad=trunc(oh*a/2)*2:160:-1:-1 -an -vsync vfr {{out_1}}",
  "input_files": {
    "in_1": "https://storage.rendi.dev/sample/sample.avi"
  },
  "max_command_run_seconds": 300,
  "output_files": {
    "out_1": "output1.gif"
  },
  "vcpu_count": 8
}'
{
  "command_id": "123e4567-e89b-12d3-a456-426614174000"
}

Authorizations

​
X-API-KEY
string
header
required

Body

application/json

Request model for submitting a single FFmpeg command.

This model allows submitting an FFmpeg command with input and output file specifications. Input file aliases must start with 'in_' and direct to a publicly accessible file, and output file aliases must start with 'out_' and only name a file name to be created.

If you're using an automation platform where curly brackets are used special as characters (like make.com, zapier, or other) add backslashes before the curly brackets, for example, replace {{in_1}} with backslashes and brackets \{\{in_1\}\}.

Response

200
application/json

Successfully submitted FFmpeg command

Response model for command submission.

Contains the unique identifier assigned to the submitted command that can be used to poll for status and retrieve results.