Source media for content repurposing
Prepare source media for reuse across publishing workflows. Retrieve the file once for your own editing process, then track the derivatives your application creates.
The Challenge
Prepare source media for reuse across publishing workflows. Retrieve the file once for your own editing process, then track the derivatives your application creates.
Availability depends on the source, access restrictions and supported output options. Test representative URLs and review the API documentation. Submit content you are authorized to use; access to a public URL does not grant rights to reuse it.
Check the job’s final status and failure details. Source restrictions, unavailable media or delivery configuration can prevent completion. Resolve the reported cause before retrying; after a request timeout, check the existing job before creating another.
From a source URL to a file your product can use.
Retrieve an editable source
Test the media output against your editing tools before importing a wider collection. Your application determines the formats and versions required by each publication channel.
Maintain derivative relationships
Keep each edited version linked to the source file and job. This makes it possible to identify which exports need rebuilding if the source changes or a download is replaced.
Own the publication workflow
Editing, captioning, review and publishing remain in your application. Record their statuses separately so a successful download is not mistaken for content that has already been published.
How Tornado API works
Know what to expect.
Where are my files stored?
Use platform storage for the default delivery flow or configure a supported cloud destination, including S3-compatible storage, GCS, Azure Blob, Alibaba OSS or Google Drive. Destination permissions and retention settings matter.
Does an expired download link mean the file was deleted?
No. Link expiry controls access through that URL. File retention and deletion are separate. Store a copy in a destination you control when you need lasting access.
What happens when a job fails?
Check the job’s final status and failure details. Source restrictions, unavailable media or delivery configuration can prevent completion. Resolve the reported cause before retrying; after a request timeout, check the existing job before creating another.
How is usage billed?
Billing uses billable volume under your account’s plan. A billing floor can make it differ from the delivered file size, especially for audio or clips. Billing in the dashboard shows your active rate, allowance and usage.
Ready to Scale Your Pipeline?
Start with one source URL and check the delivered result.