SFTPGo Octri Preview
PATCH/shares-chunked-uploads/{id}

Upload a chunk to a share

Uploads a chunk of binary data, or the entire file, to an existing share upload. Send the chunk with the required Tus headers, including an Upload-Offset that matches the server's current offset. For password-protected shares, authenticate with HTTP Basic using the share password; the password is revalidated on every request.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

5 parameters
idstringrequired
The unique upload identifier generated by the server when the upload is created.
Tus-Resumablestringrequired
The Tus protocol version. Must be `1.0.0`.
Allowed:1.0.0
Upload-Offsetintegerrequired
The chunk's starting offset in the upload. Must match the current offset on the server.
Content-Typestringrequired
The chunk media type. Must be `application/offset+octet-stream`.
Allowed:application/offset+octet-stream
Content-Lengthintegerrequired
The size of the chunk in bytes.

4 status codes
204Returns confirmation that the chunk was accepted; the response has no body.
404Returned when the upload ID is invalid.
409Returned when the `Upload-Offset` does not match the current server offset. Send a HEAD request to get the current offset, then retry.
415Returned when the `Content-Type` is not `application/offset+octet-stream`.

Error handling

A 404 is returned when the id path parameter is invalid; a 409 when the Upload-Offset header does not match the server's current offset; a 415 when the Content-Type header is not application/offset+octet-stream. The Tus-Resumable header must be 1.0.0, and Content-Length must match the chunk's size in bytes.