Sluby
REST APIUploads

Send upload bytes (tus).

PATCH
/api/v1/uploads/{id}

Authorization

bearerAuth
headerAuthorizationBearer <token>

A Sluby API key (sluby_...) sent as Authorization: Bearer <key>. Keys carry scopes: upload, read, manage.

Path Parameters

id*string

Upload id, the last segment of Location.

Header Parameters

Tus-Resumable*unknown
Upload-Offset*integer

Request Body

application/offset+octet-stream

Response Body

Accepted; Upload-Offset is the new offset.

Example Request
curl -X PATCH 'https://sluby.example.com/api/v1/uploads/string' \  -H 'Tus-Resumable: 1.0.0' \  -H 'Upload-Offset: 0'
Example Response
Empty

Upload status. GET

Previous Page

Cancel an upload in progress. DELETE

Without Tus-Resumable this is the REST cancel: the partial file and the asset the upload created are removed, and the session is marked cancelled (200). With Tus-Resumable it is a tus termination, which does the same and answers 204. A finished upload is the source its asset is processed and retried from and cannot be cancelled: REST answers 409, tus 400; delete the asset instead (manage scope).