COMING SOON - The application key APIs are under development, and will be available soon.

b2_delete_key

Deletes the application key specified.

Request

Request HTTP Headers

Authorization

required

An account authorization token, obtained from b2_authorize_account. The token must have the deleteKeys capability.

Request HTTP Message Body Parameters

applicationKeyId

required

The key to delete.

Response

Response HTTP Status 200

Key successfully deleted. The JSON response will contain:

accountId

required

The account that this application key is for.

applicationKeyId

required

The ID of the key.

keyName

required

The name assigned when the key was created.

capabilities

required

A list of strings, each one naming a capability the key had. Possibilities are: listKeys, writeKeys, deleteKeys, listBuckets, writeBuckets, deleteBuckets, listFiles, readFiles, shareFiles, writeFiles, and deleteFiles.

expirationTimestamp

optional

When present, says when this key will expire, in milliseconds since 1970.

bucketId

optional

When present, restricts access to one bucket.

namePrefix

optional

When present, restricts access to files whose names start with the prefix

Response Errors

Key not deleted. If possible the server will return a JSON error structure. Errors include:

status

code

message

400

bad_request

No Authorization header

400

bad_request

Application key does not exist

401

unauthorized

Not authorized