hosting

DELETE /v1/storage/buckets/{bucketId}

Forget a bucket.

All hosting endpoints

Authentication

Send an API key as a bearer token. The key must carry the storage.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X DELETE https://api.zinndigital.com/v1/storage/buckets/{bucketId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Removes the bucket record and, for a bucket of your own, deletes its stored credential. A bucket still serving media for one or more sites answers `422` and names them: deleting it would leave every rewritten image URL in those sites' published posts pointing at a bucket the platform no longer knows about, and the person pressing delete on a storage screen has no way to know that. Turn media offload off on those sites first. Requires `storage.manage`.

Parameters

NameTypeRequiredWhat it is
bucketId (path)stringYesThe bucket's id.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429