Files API
Checkpoint Upload Parts
Persist part_tokens for completed parts so they can be skipped on resume
POST
Overview
Checkpoint a subset of an upload’s completed parts. The server stores eachpart_token (the ETag returned from a successful part PUT) so that:
- A later Initiate Upload call with
resume_if_started=trueskips the checkpointed parts and only returns presigned URLs for the remaining ones. - Checkpointed parts do not need to be re-supplied on the Complete Upload call.
Direct-to-cloud file uploads support files up to 250GB.
Path Parameters
Upload identifier returned by Initiate Upload
Request Body
Completed parts to checkpoint
Response
Number of parts that were newly checkpointed (equal to the number of parts in the request after validation)