FFmpeg Command API
API for running FFmpeg in a cloud environment
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
API for running FFmpeg in a cloud environment
Endpoints 13
API
- GETGet Command Status
/v1/commands/:command_idGet the status of a previously submitted FFmpeg command. Works for regular commands and chained commands. - GETGet list of commands sent
/v1/commandsGet the statuses of a previously submitted FFmpeg commands, ordered by creation time - descending. - POSTRun FFmpeg Command
/v1/run-ffmpeg-commandSubmit an FFmpeg command for processing with input and output file specifications. - POSTRun Chained FFmpeg Commands which share input and output files
/v1/run-chained-ffmpeg-commandsSubmit multiple FFmpeg commands where following commands can depend on output of previous commands. Running chained FFmpeg commands is faster than running… - POSTFFprobe and store a file
/v1/files/store-fileSubmit a file to be analyzed with FFprobe and stored in Rendi's storage. You can use this endpoint both to get metadata about a file and to store it. If you… - POSTInitiate a direct multipart upload
/v1/files/init-uploadStart uploading a local file directly to Rendi's storage. Returns a per-part list of presigned PUT URLs that you upload chunks to. See the direct upload guide… - POSTComplete a multipart upload
/v1/files/:file_id/complete-uploadFinalize a direct upload started via POST /v1/files/init-upload. The file then goes through FFprobe for media metadata; status changes as UPLOADED and becomes… - POSTAbort a multipart upload
/v1/files/:file_id/abort-uploadCancel a direct upload started via POST /v1/files/init-upload. Discards any parts already uploaded to storage and marks the file as failed. See the direct… - GETGet list of all stored files
/v1/filesGet the list of all stored files for an account, ordered by creation time - descending. Can return command output files or stored files. Will not return… - GETGet Stored File
/v1/files/:file_idGet a stored file and its FFprobe metadata by its ID. Can return a command output file or a stored file. File can be deleted, in which case will still return… - DELETEDelete Stored File in Rendi
/v1/files/:file_idDelete a stored file in Rendi - DELETEDelete Command Files
/v1/commands/:command_id/filesDelete all stored output files associated with a command - POSTBulk Delete Stored Files
/v1/files/bulk-deleteDelete multiple stored files in a single request
API details
- Base URL
https://api.rendi.dev- Authentication
- An API key in the X-API-KEY header
- Operations
- 13 operations on 12 pathsPOST 7GET 4DELETE 2
- Main resources
- API 13File Management 9FFmpeg Commands 4
- Response formats
application/json- Description format
- OpenAPI 3.1.0, API version
1.0.0 - Links
- OpenAPI document
- Listed from
- Rendi's published OpenAPI description
How to test the FFmpeg Command API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the FFmpeg Command API collection, without the publisher's secrets.
- Add your credentialsThis API uses an API key in the X-API-KEY header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Get Command Status” (GET /v1/commands/:command_id), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the FFmpeg Command API?
API for running FFmpeg in a cloud environment It is listed under Media & content and has 13 endpoints.
Who publishes the FFmpeg Command API?
It is listed from Rendi's public API description (an OpenAPI document), not published by Rendi on Swastik Codes. Anyone who controls rendi.dev can claim the profile by adding a DNS TXT record.
What is the base URL of the FFmpeg Command API?
Requests go to https://api.rendi.dev. Endpoint paths are added to this base URL.
How do I authenticate with the FFmpeg Command API?
With an API key in the X-API-KEY header.
How many endpoints does the FFmpeg Command API have?
13 operations on 12 paths (7 POST, 4 GET, 2 DELETE). The largest groups are API, File Management, FFmpeg Commands.
Is forking the FFmpeg Command API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.