Using a presigned S3 URL to upload large files (API users)

Large uploads go direct to cloud storage via presigned URLs. This keeps the API fast and reliable for automation moving multi-gigabyte conference recordings.

Flow overview

1. Call the uploads endpoint with file metadata to receive an upload id and presigned PUT URL.
2. PUT your binary directly to storage from your server or trusted client.
3. Pass the upload id when starting a clip job via the API.

Why presigned URLs

Your app uploads multi-gigabyte video without proxying through Choppity servers. Less timeout risk and lower latency worldwide compared to multipart POST through a single region.

Requirements

Use HTTPS PUT within the expiry window. Match the content type you declared at registration. Failed uploads need a fresh presigned URL; do not retry stale links.

Docs

See docs.choppity.com for request schemas, expiry times, and error codes returned when metadata does not match the bytes uploaded.