Copy video data from an HTTPS URL into the Pixop Platform

Copies video data from an HTTPS URL into the Pixop Platform, making it available for processing.

A new master video record is created for the selected team, and an asynchronous multipart copy operation from the provided HTTPS URL to Pixop is initiated.
The URL must support range requests and remain accessible for the entire duration of the copy process.

The status of the copy operation can be tracked using:

• GET /v1/videos/{videoId}/in/status
• GET /v1/videos/{videoId} (for full video details)
• Webhooks: Subscribe to video_in and/or video_in_ingestion events to receive real-time updates

The videoId is returned in the response.

Workflow:

1. Copy Operation: Once complete, the status updates to DONE.
2. Ingestion Process: If FullIngestion is true, Pixop extracts thumbnails, full frames, and a web video.
3. Free 10-Second Clip: Unless disabled for the team, a free 10-second clip is automatically created and becomes available via GET /v1/videos/{videoId}/derived.
   This clip is treated as a separate video and will trigger its own clip_processing and clip_ingestion webhook events under a new videoId.

Notes:

• If the video size exceeds 500 GB, a 400 Bad Request response is returned.
• A 400 Bad Request may also be returned if the URL is invalid, inaccessible, or does not support range requests.