Use case
A media pipeline you do not have to run yourself
Your users upload videos and images, FlowData turns them into the outputs your application needs. No encoder servers of your own, billed per output.
For businesses and self-employed professionals only
From upload to finished file
Fetch a source, create a job, wait for the webhook. The basic pattern never changes.
-
Provide the source
Use a public
httpsaddress or upload the file directly throughPOST /v1/media/uploadswith a signed address. -
Create a job
POST /v1/media/jobswith pipeline and outputs answers at once with202and an ID.{ "pipeline": "ugc_video", "input": { "url": "https://files.example.com/in.mov" }, "outputs": { "clean": { "managed": true } } } -
Wait for the webhook
As soon as the job is done, the signed event arrives at your registered endpoint, with status and outputs.
-
Deliver the outputs
Download finished files from FlowData within 7 days, or have them go straight into your own storage with
put_url.
What this gives you in practice
Repeatable
An
Idempotency-Keyprevents duplicate jobs on network errors or retries.Consistent
Team presets and watermarks make every output look the same, wherever it came from.
Predictable
The expected maximum is reserved when a job is created. Spending limits per key cap what a faulty loop can cost.
Frequently asked questions
course_video up to 3 hours and 5 GB.
put_url.