multipart/form-data POST request to /api/v1/videos/upload. The response returns a video_id you pass when creating a processing job.
Supported formats and limits
| Property | Value |
|---|---|
| Accepted formats | mp4, mov, avi, mkv, webm |
| Maximum file size | Configurable (default: 1000 MB) |
Request fields
The video file to upload. Must be one of the supported formats.
The
video_id of a previously uploaded template video. When provided, Clipzy uses this video’s style as the reference when you create a job. You can also supply this when creating the job instead.A URL that Clipzy calls when a job using this video completes. See Webhooks for payload details.
Upload a video
Prepare your file
Confirm your file is in a supported format (
mp4, mov, avi, mkv, or webm) and within the size limit configured on your deployment (default: 1000 MB).Read the response
A successful upload returns HTTP Save the
200 with the following body:video_id — you need it to create a processing job.Response fields
Unique identifier for the uploaded video. Pass this to
POST /api/v1/jobs as video_id.The original filename as received by the server.
Size of the uploaded file in bytes.
Technical properties extracted from the video file.
ISO 8601 timestamp of when the upload completed.
Internal storage path for the uploaded file.
Error cases
Errors follow the standard error format:Unsupported format
Unsupported format
If the file extension or MIME type is not supported, the API returns HTTP
422 with code: "UNSUPPORTED_FORMAT". Convert your file to mp4, mov, avi, mkv, or webm before retrying.File too large
File too large
Files exceeding the
MAX_FILE_SIZE_MB limit return HTTP 413 with code: "FILE_TOO_LARGE". Compress or trim your video, or ask your administrator to increase the limit.Missing file field
Missing file field
Omitting the
file field returns HTTP 422 with code: "MISSING_FIELD". Ensure your multipart body includes a file part.Next steps
Once you have avideo_id, create a processing job to start style analysis and rendering.