Skip to main content
POST
Acknowledge an uploaded chunk, extending the deadline and getting the next chunk's URL

Authorizations

Authorization
string
header
required

Use a Bearer token for authentication. Submit the token using the Authorization header: Authorization: Bearer <token>.

Path Parameters

username
string
required

The username associated with the request.

namespace
string
required

Namespace for the dataset.

assetId
string<uuid>
required

The data asset's id.

versionNo
integer
required

The version number.

partNumber
integer
required

The 1-based chunk number that finished uploading.

Response

Part accepted; deadline extended

assetId
string<uuid>
required
versionNo
integer
required
uploadId
string
required
partSize
integer<int64>
required
totalParts
integer
required
expiresAt
string<date-time>
required

Upload deadline. Each acknowledged part pushes it out.

next
object[]
required

Part URLs to upload next, and the authority on how many may be in flight - it can be fewer than the requested concurrency. Empty once every part number has been handed out, which is not the same as every part having been uploaded: the server tracks only how many it has issued, never what landed. The client is the sole authority on its own progress. To re-obtain a URL it dropped or let expire, use the parts/presign endpoint.