- Print
- DarkLight
b2_authorize_account
- Print
- DarkLight
Returns an authorization token
Used to log in to the B2 API. Returns an authorization token that can be used for subsequent API calls, and a URL that should be used as the base URL for subsequent API calls.
You can use either the master application key or a normal application key.
NOTE the account ID can be used in place of the master application key ID.
You'll find the master application key in the Backblaze web UI. When using the master application key, use your "master application key ID" and the "application key" you got from the site.
Master Application Key This is the first key you have access to, it is available in the Backblaze web UI. This key has all capabilities, access to all buckets, and has no file prefix restrictions or expiration.
Application Key(s) [non-master] These are other keys created by you and can be limited to a bucket, with a specific file prefix and can expire.
Normal application keys come from the b2_create_key call. When using one of them, the "application key ID" and "application key" are the ones returned when you created the key.
API Versions
v2 Return bucket name (Sept 13, 2018)
When using an application key with a bucket restriction, the name of the bucket is now returned.
An HTTP basic auth value constructed as follows:
- The application key id and application key are combined into a string in the format "applicationKeyId:applicationKey".
- The combined string is Base64 encoded.
- "Basic" is put before the encoded string.
The request succeeded.
The identifier for the account.
An authorization token to use with all calls, other than b2_authorize_account, that need an Authorization header. This authorization token is valid for at most 24 hours.
An object (see below) containing the capabilities of this auth token, and any restrictions on using it.
A list of strings, each one naming a capability the key has. Possibilities are: listKeys
, writeKeys
, deleteKeys
, listBuckets
, writeBuckets
, deleteBuckets
, listFiles
, readFiles
, shareFiles
, writeFiles
, and deleteFiles
.
When present, access is restricted to one bucket.
When bucketId
is set, and it is a valid bucket that has not been deleted, this field is set to the name of the bucket. It's possible that bucketId is set to a bucket that no longer exists, in which case this field will be null. It's also null when bucketId is null.
When present, access is restricted to files whose names start with the prefix
The base URL to use for all API calls except for uploading and downloading files.
The base URL to use for downloading files.
The recommended size for each part of a large file. We recommend using this part size for optimal.
The smallest possible size of a part of a large file (except the last one). This is smaller than the recommendedPartSize
. If you use it, you may find that it takes longer overall to upload a large file.
DEPRECATED: This field will always have the same value as recommendedPartSize
. Use recommendedPartSize
instead.
The base URL to use for all API calls using the S3 compatible API.
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. |
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 | unauthorized | The applicationKeyId and/or the applicationKey are wrong. |
401 | unsupported | The applicationKeyId is valid, but cannot be used with this version of the B2 API. The message contains information about the problem. |
status | code | description |
---|---|---|
403 | transaction_cap_exceeded | Transaction cap exceeded. To increase your cap, sign in to your B2 Cloud Storage account online. Then select the Caps & Alerts link in the B2 Cloud Storage section of the sidebar. |