Skip to main content

Ingest Footage and Files

When you compose a video edit you provide URLs to source footage. These URLs can be anywhere on the internet and will be ingested (downloaded) as part of the rendering process.

While convenient, this approach comes with a number of disadvantages:

  • Latency due to the file being located in a different geographical region from the Edit API.
  • Latency due to slow server, storage location or network issues.
  • Outgoing bandwidth costs every time the file is requested.
  • The need to setup, maintain and manage your own storage and server.
  • Setting up a system to process customer uploads.
  • Dealing with CORS issues.

The Ingest API solves these issues by providing endpoints to fetch or upload source assets (videos, images, audio and fonts) that can be used in your edit.