Uploads

Complete upload

Completes the Upload.

Within the returned Upload object, there is a nested File object that is ready to use in the rest of the platform.

You can specify the order of the Parts by passing in an ordered list of the Part IDs.

The number of bytes uploaded upon completion must match the number of bytes initially specified when creating the Upload object. No Parts may be added after an Upload is completed. Returns the Upload object with status completed, including an additional file property containing the created usable File object.

post/uploads/{upload_id}/complete

Path parameters

upload_idstring required

Example:upload_abc123

The ID of the Upload.

Request body

part_idsstring[] required

The ordered list of Part IDs.

md5string

The optional md5 checksum for the file contents to verify if the bytes uploaded matches what you expect.

Response

idstring required

The Upload unique identifier, which can be referenced in API endpoints.

created_atinteger required

The Unix timestamp (in seconds) for when the Upload was created.

filenamestring required

The name of the file to be uploaded.

bytesinteger required

The intended number of bytes to be uploaded.

purposestring required

The intended purpose of the file. Please refer here for acceptable values.

status'pending' | 'completed' | 'cancelled' | 'expired' required

The status of the Upload.

expires_atinteger required

The Unix timestamp (in seconds) for when the Upload will expire.

object'upload'

The object type, which is always "upload".

Changes

Changed in 9 of the 163 revisions of this API.17326

Sep 25, 2026cda988e2e3645See the full diff
- ○
  added the non-success response with the status
  response-non-success-status-added
- ○
  added the non-success response with the status
  response-non-success-status-added
- ○
  added the non-success response with the status
  response-non-success-status-added
- ○
  added the non-success response with the status
  response-non-success-status-added
- ○
  added the non-success response with the status
  response-non-success-status-added
May 13, 202674cbcf73838f1See the full diff
- ●
  added the new user_data enum value to the // response property for the response status
  response-property-enum-value-added
This revision also has 40 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Mar 11, 20256ab43fe7798e1See the full diff
- ○
  added the optional property // to the response with the status
  response-optional-property-added
Jan 31, 2025fc164a27fdb9711See the full diff
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ○
  added subschema #2 to the response property allOf list for the response status
  response-property-all-of-added
Jan 31, 202515156e46769c19See the full diff
- ▲
  the response property became nullable for the status
  response-property-became-nullable
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  removed subschema #2 from the response property allOf list for the response status
  response-property-all-of-removed
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
Jan 22, 2025bdebcdfcbbde711See the full diff
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ▲
  removed the required property / from the response with the status
  response-required-property-removed
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ○
  added subschema #2 to the response property allOf list for the response status
  response-property-all-of-added
Jul 19, 2024837775c0b9881See the full diff
- ▲
  the response property became optional for the status
  response-property-became-optional
Jul 19, 202446964092fbe11See the full diff
- ○
  the response property became required for the status
  response-property-became-required
Jul 18, 2024bddc980d3fbb18See the full diff
- ▲
  the response's property type changed from object to no type for status
  response-property-type-changed
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added
- ○
  added the required property / to the response with the status
  response-required-property-added

Full history