- Print
- DarkLight
b2_reserve_trial_create_account
- Print
- DarkLight
This operation creates a new Backblaze B2 account and starts a B2 reserve trial.
A B2 Reserve Trial gives an end user time-limited access to all of B2 Reserve's product features for evaluation.
New Backblaze accounts will receive an invitation email asking them to reset their password. The account will be fully functional and can be closed or converted to a paid account at the end of the B2 Reserve Trial.
Backblaze will pick a region if not specified. There are currently 3 regions available: us-west
, us-east
, eu-central
.
The duration (in days) of the trial period. This value must be between 7 and 30 (inclusive).
The amount of storage required in TB. This value must be between 1 and 20 (inclusive).
The request succeeded.
Account Id of the newly created B2 account
An application key for the new account that can be used to call Backblaze B2 APIs. This application key only has access to the bucket returned in the response. This key is also limited to API calls that read, write, and delete files, as well as update bucket settings.
An application key ID for the new account.
The endpoint domain for Backblaze S3-Compatible API. The endpoint has the format: s3.<region>.backblazeb2.com
The trial start date uses the ISO 8601 date format (yyyy-MM-dd). The date is in the UTC timezone.
The trial end date is calculated by adding the start date plus the number of days in the terms of the request. Trials expire at the start of the day.
The end date uses the ISO 8601 date format (yyyy-MM-dd). The date is in the UTC timezone.
Bucket name that is accessible using the returned application key. Used with the Backblaze S3-Compatible API.
Bucket ID that is accessible using the returned application key. Used with the B2 Native API.
status | code | description |
---|---|---|
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 auth token used is not valid. Call b2_authorize_account again to either get a new one, or an error message describing the problem. This occurs when the Authorization header is passed in with an invalid token. For example, Authorization: 000 . In this case 000 is invalid. |
status | code | description |
---|---|---|
403 | access_denied | The auth token is valid but does not authorize this call with these parameters. The accountId may not be enabled for Partner API, may not have a valid phone number on their account, or their account may not be in good standing. |
403 | access_denied | The auth token is missing and the request is not entitled. The proper Authorization: |