Files

Finalize a block based file upload job

Changed on Feb 25, 2026

This endpoint finalizes the block upload process by initiating an asynchronous job that will merge all uploaded blocks and creates the final file asset. In case of asynchronous operation success, the asset field will contain the newly created file's metadata as defined by File Schema.

NOTE:

Validation and Behavior for Finalize (Block-Based Upload)

The following rules govern how the server interprets the finalization request for a block-based upload:

File Size in Initialization

The size provided during the initiate request is treated as an estimate, not a strict validation boundary.

Clients are not penalized if the actual uploaded content size differs from the declared size.

In future, clients will be able to extend block sets if their initial estimate is too low (see Future Enhancements).

Skipped Blocks

Clients are allowed to skip any block from the original transferLinks list, as long as part numbers remain ordered and are accurately reported in the usedTransferLinks array during finalize.

Skipped parts should simply be omitted from usedTransferLinks.

Finalization is based on:

The used part numbers explicitly listed in the usedTransferLinks array.

The server will stitch together content in the order of these part numbers.

Any parts not listed will be ignored even if data was uploaded to them.

post/files/upload/finalize

Request

Base URL: https://cloudstorage.adobe.io/v1
URL: https://cloudstorage.adobe.io/v1/files/upload/finalize
Auth: HTTP bearer

Headers

x-request-idstring

Example:1234567890

The X-Request-Id header is used to identify a request.
It can be used to correlate logs and other resources and is intended to be a non-persistent identifier.

Request body

uploadIdstring required

The upload id

usedTransferLinksnumber[] required

The transfer links used to upload the file

Example request

{
  "uploadId": "123e4567-e89b-12d3-a456-426614174000"
}

Response

Success - Asynchronous job id used to call the status endpoint.

jobIdstring

The asynchronous job id

Example response

{
  "jobId": "123e4567-e89b-12d3-a456-426614174000"
}

Changes

Feb 25, 2026240b6278279c Revision changes
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
- warning
  added the new conflict enum value to the response property for the response status
Dec 18, 202501600f5358e9 Revision changes
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new operation_timeout enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new payload_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status
- warning
  added the new resource_too_large enum value to the response property for the response status

Operation history (4 revisions)