post https://api.pixop.com/api/v1/videos/in/s3
Copies video data from an S3 bucket 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 S3 bucket to Pixop is initiated.
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_inand/orvideo_in_ingestionevents to receive real-time updates
The videoId is returned in the response.
Workflow:
- Copy Operation: Once complete, the status updates to
DONE. - Ingestion Process: If
FullIngestionistrue, Pixop extracts thumbnails, full frames, and a web video. - 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 ownclip_processingandclip_ingestionwebhook events under a newvideoId.
Note:
- If the video size exceeds 500 GB, a
400 Bad Requestresponse is returned. - A
400 Bad Requestmay also be returned for other reasons, such as invalid credentials. - A
404 Not Foundresponse is returned if the bucket, or object does not exist.
