Files API
Complete Upload
Finalize a direct-to-cloud upload after all parts have been uploaded
POST
Overview
Finalize a direct-to-cloud upload after the client hasPUT every part to its presigned URL. The server validates the supplied part_tokens, assembles the final file, and registers it with the organization.
Parts already submitted via Checkpoint Upload Parts do not need to be repeated here — only supply tokens for parts not yet checkpointed.
Direct-to-cloud file uploads support files up to 250GB.
Path Parameters
Upload identifier returned by Initiate Upload
Request Body
Completed parts that have not already been checkpointed. Pass an empty array when every part of the upload has been checkpointed.
Optional whole-file checksum, base64-encoded. When provided, the server queries the storage backend for the checksum it computed over the full object and compares; a mismatch marks the file as corrupt and returns an error. Omit to skip verification entirely.The encoding and byte length must match the algorithm returned by Initiate Upload (e.g.
crc32c → 4 raw bytes → 8 base64 characters with = padding). Sending a checksum when integrity_algorithm: none is returned is an error.Response
Internal unique identifier of the completed file
Name of the completed file
Total size of the completed file in bytes
Lifecycle status of the file. After a successful upload, the status is
Registered. Other values are: Unknown, Uploading, Ingested, Deleting, Deleted, and Corrupt.The format of the status string returned for direct-to-cloud uploads is different from the
file_status string returned by the Get File Metadata endpoint.Type-specific attributes for the file. Shape depends on the file type — see Get File Metadata for the variants.