The Wasabi Account Control API (WACA), formerly known as the Wasabi Partner API, enables you to manage multiple Wasabi accounts using API methods. If you do not want to use the API and, instead, want to use Wasabi's hosted, pre-built platform, refer to the Wasabi Account Control Manager.
Below are several FAQs about the Wasabi Account Control API:
What is the Wasabi Account Control API?
The Wasabi Account Control API is a RESTful API that allows for the following functions:
Create a new Sub-Account that is linked to the partner’s Wasabi account.
Generate AWS key sets for Sub-Accounts.
Manage Sub-Account trial parameters, such as extending the Sub-Account trial period and changing Sub-Account trial quotas.
Convert a Sub-Account trial period into a full (paying) account.
Query utilization of Sub-Accounts both at the summary account level and bucket level.
Query invoices of Sub-Accounts.
Delete Sub-Accounts.
Manage account “profile” information, such as email address.
What is the difference between the Wasabi Account Control API and WACM?
Wasabi Account Control Manager leverages the Wasabi Account Control API and an easy-to-use interface for account management without the need for development. However, if developing your medium for managing Wasabi accounts is your preferred approach, the Wasabi Account Control API is right for you.
How can I get started using the Wasabi Account Control API?
To get started using the Account Control API, contact a Wasabi Sales Representative at sales@wasabi.com.
What is the relationship between my Wasabi account and an account created with the Wasabi Account Control API?
Your Wasabi account will become the Control Account that is associated with billing. Accounts created on the Wasabi Account Control API are Sub-Accounts related to your Control Account. Sub-Accounts are Wasabi storage accounts whose administration (billing, password resets, and so on) is managed by you.
How am I billed when using the Wasabi Account Control API?
You are billed as you normally would be through your main Wasabi account. The only difference is that you will be billed for the storage consumption of your Sub-Accounts in addition to your main Wasabi account (Control Account).
How are consumers billed when created with the Wasabi Account Control API?
The Sub-Accounts associated with your main Wasabi account (Control Account) have their billing rolled up to your account. You will receive one bill for yourself and all of your Sub-Accounts. Your Sub-Accounts will not be billed individually.
How can I determine the amount of storage used by consumers?
To return the daily storage and data transfer associated with the Sub-Account across all buckets in the Sub-Account, use:
GET /v1/accounts/<AcctNum>/utilizationsUsing from and to query string parameters (in the format YYYY-MM-DD) will apply date filters to the result set.
What is the difference between a Wasabi Account Control API key and an S3 API key?
Wasabi Account Control API keys are a unique keyset of primary and secondary keys that are used only to create and manage your Wasabi Account Control API implementation. Each Wasabi account does not necessarily gain access to the Wasabi Account Control API keyset.
S3 API keys are a unique keyset of Active and Secret keys that are used only to manage your storage account. Each Wasabi account is entitled to a minimum of one pair of S3 keys.
What is the difference between a primary and secondary Wasabi Account Control API key?
Primary and secondary API keys provided by Wasabi are not different in terms of entitlement. Either of the keys can be used for Wasabi Account Control API implementation.
How do I check all the Sub-Accounts I have created?
I created a Sub-Account using the API and, when I log into my Control Account, I don’t see it listed there. How do I check all the Sub-Accounts I have created?
From a storage perspective, a control Wasabi account is not different from a Sub-Account. Control Accounts will NOT display the Sub-Accounts created via the Wasabi Account Control API interface. The only way to list all the Sub-Accounts created is by performing a GET /v1/accounts operation using your existing Wasabi Account Control API implementation.
How do I see account information for a specific Sub-Account?
To see Sub-Account information, you must pass the GET /v1/accounts/<AcctNum> operation. Inputting the correct account number for the account in question will return details about that account.
What happens if I choose to cancel my Wasabi Account Control API subscription?
A Wasabi Account Control API subscription can be canceled at any time.
What happens to my existing Sub-Accounts when I cancel my subscription?
At cancellation, account control API keys are no longer valid. Any Sub-Accounts created while the subscription was active will continue to operate as before; however, the Control Account will lose the ability to manage (update, delete, reset S3 API keys, and so on) all of the Sub-Accounts, including access to sub-invoice data.
What is Wasabi's recommended approach to cancel a Wasabi Account Control API subscription?
Before canceling a Wasabi Account Control API subscription, consider deleting all Sub-Accounts. But first, export all sub-invoice data set so any pending charges that your customer owes can be recovered. When Sub-Accounts are deleted, all associated data stored in the Sub-Account will also be purged, including sub-users, access keys, IAM policies, and so on.