For each chunk of content in a set within a transfer operation, use this endpoint to copy the chunk to the destination environment after using the corresponding Retrieve a specific chunk of transfer data endpoint, where you obtained a binary stream representing the chunk data.
Make this request in your destination environment.
Set the request header Content-Type: application/octet-stream.
The request body for this endpoint must be the raw binary stream obtained from the response of the paired endpoint.
Do not alter, wrap, re-encode or chunk the stream; forward it exactly as received:
- For media chunks, the client must send the compressed bytes as-is, with no decompression.
- For content (non-media) chunks, the client must send the encrypted bytes as-is, with no decryption.
After retrieving and transferring all the chunks in a particular set, use the Complete a chunk set endpoint to generate a .raif file containing that chunk set's data on the destination environment.
The unique identifier of the transfer operation. This is the UUID you provided when you created a content transfer operation.
Whether the chunk contains media content, affecting whether the data is compressed (media) or encrypted (non-media). For a given chunk, obtain this value from the IsMedia parameter in the Content-Disposition response header of the Retrieve a specific chunk of transfer data endpoint.
- https://your-environment.sitecorecloud.iohttps://your-environment.sitecorecloud.io/sitecore/api/content/transfer/v1/transfers/{transferId}/chunksets/{chunksetId}/chunks/{chunkId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://your-environment.sitecorecloud.io/sitecore/api/content/transfer/v1/transfers/{transferId}/chunksets/{chunksetId}/chunks/{chunkId}?isMedia=true' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/octet-stream' \
-d string