- Print
- DarkLight
b2_delete_bucket
- Print
- DarkLight
Deletes the bucket specified
Only buckets that contain no version of any files can be deleted.
API Versions
v1: Application keys (July 26, 2018)
Incompatible change: After calling b2_authorize_account with an application key that does not have the right permissions, this call will return a 401 Unauthorized.
v1: Original release (September 22, 2015)
PLEASE NOTE:
This API endpoint can be called using a GET
request by converting the parameters in the request body to query parameters.
An account authorization token, obtained from b2_authorize_account.
The token must have the deleteBuckets
capability.
Your account ID.
The ID of the bucket to delete.
The request succeeded.
The account that the bucket is in.
The unique ID of the bucket.
The unique name of the bucket.
One of: allPublic, allPrivate
, restricted
, snapshot
, shared
, or other values added in the future. allPublic
means that anybody can download the files is the bucket; allPrivate
means that you need an authorization token to download them; snapshot
means that it's a private bucket containing snapshots created in the Backblaze web UI.
The user data stored with this bucket.
The initial list (a JSON array) of CORS rules for this bucket. See CORS Rules for an overview and the rule structure.
The Object Lock configuration for this bucket. This field is filtered based on application key capabilities; readBucketRetentions
capability is required to access the value. See Object Lock for more details on response structure.
The default bucket Server-Side Encryption settings for new files uploaded to this bucket. This field is filtered based on application key capabilities; readBucketEncryption
capability is required to access the value. See Server-Side Encryption for more details on response structure.
The initial list (a JSON array) of lifecycle rules for this bucket. See Lifecycle Rules.
The list of replication rules for this bucket. See Cloud Replication Rules for an overview and the rule structure.
A counter that is updated every time the bucket is modified, and can be used with the ifRevisionIs
parameter to b2_update_bucket to prevent colliding, simultaneous updates.
When present, contains a set of strings. Reserved for future use.
status | code | description |
---|---|---|
400 | bad_bucket_id | The requested bucket ID does not match an existing bucket. |
400 | bad_request | The request had the wrong fields or illegal values. The message returned with the error will describe the problem. |
400 | cannot_delete_non_empty_bucket | A bucket must be empty before it can be deleted. To delete this bucket, first remove all of the files in the bucket, then try the delete operation again. |
The numeric HTTP status code. Always matches the status in the HTTP response.
A single-identifier code that identifies the error.
A human-readable message, in English, saying what went wrong.
status | code | description |
---|---|---|
401 | bad_auth_token | The auth token used is not valid. Call b2_authorize_account again to either get a new one, or an error message describing the problem. |
401 | expired_auth_token | The auth token used has expired. Call b2_authorize_account again to get a new one. |
401 | unauthorized | The auth token used is valid, but does not authorize this call with these parameters. The capabilities of an auth token are determined by the application key used with b2_authorize_account. |