Initiates an asynchronous multipart copy operation to transfer video data from the Pixop Platform to the specified S3 bucket.

• The video data is not ready for copy until the processing task is complete.
  You can check the status of the processing task using GET /v1/videos/{videoId}/processing/status (or GET /v1/videos/{videoId}/in/status for a "video in" copy operation), or subscribe to clip_processing, video_processing or video_in webhooks to receive real-time updates.

The status of this operation can be tracked using:

• GET /v1/videos/{videoId}/out/status

• GET /v1/videos/{videoId} (for full video details)

• Webhooks: Subscribe to video_out events to receive real-time updates

• When the operation succeeds, the status updates to DONE. If it fails, the status updates to FAILED.

Retry and Abandon Options:

• Restart a FAILED operation using POST /v1/videos/{videoId}/out/restart.
• Abandon a FAILED operation and free up resources using POST /v1/videos/{videoId}/out/abandon.

Notes:

• Only one "video out" operation can run per video at a time. Starting a new operation will result in a 409 Conflict response.
• If the specified object key already exists in the S3 bucket, or if the video data is not ready for copy, a 409 Conflict response is also returned.