Sluby
REST APIAssets

Delete an asset.

Soft-deletes the asset so it disappears from the API immediately, then asynchronously unpins its Sia objects and removes the record. A second DELETE answers 404.

DELETE
/api/v1/assets/{id}

Soft-deletes the asset so it disappears from the API immediately, then asynchronously unpins its Sia objects and removes the record. A second DELETE answers 404.

Authorization

bearerAuth
headerAuthorizationBearer <token>

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

Path Parameters

id*string

Asset id.

Response Body

Deletion accepted; unpin runs in the background.

application/json
  1. response
success*unknown
status*unknown

The asset is gone from the API; its Sia objects are unpinned in the background.

Example Request
curl -X DELETE 'https://sluby.example.com/api/v1/assets/string'
Example Response
{  "success": true,  "status": "deleting"}

Update asset metadata. PATCH

Changing access_tier takes effect on the delivery gateway at once. An asset being deleted answers 404, as it does to every read. Send If-Match with the ETag of the version you edited (from GET or an earlier PATCH, or built from `updated_at` as `"<epoch milliseconds>"`) and the edit applies only if nobody changed the asset since; otherwise 412 with the asset as it is now. Processing changes the version too.

Processing status for an asset. GET

Next Page