The Wasabi Account Control API (formerly known as the Wasabi Partner API or the Wasabi Account Management API, also known as WACA) enables you to manage multiple Wasabi accounts using API methods. The documentation on the API can be found here. If you do not wish to use the API and instead wish to use our hosted pre-built platform (the Wasabi Account Control Manager), more information on this platform can be found here.
Below are several FAQs pertaining to the Wasabi Account Control API:
1. What is the Wasabi Account Control API?
The Wasabi Account Control API or WACA 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 to extend the sub-account trial period and change Sub-Account trial quotas.
- Convert a Sub-Account trial period into a full (paying) account.
- Query utilization of Sub-Accounts both at summary account level and bucket level.
- Query invoices of Sub-Accounts.
- Delete Sub-Accounts.
- Manage account “profile” information, such as email address.
2. What is the difference between WACM and WACA?
Wasabi Account Control Manager leverages WACA and an easy-to-use interface to bring you account management without the need for development. However, if developing your own medium for managing Wasabi accounts is your preferred approach, the Wasabi Account Control API is right for you.
3. How can I get started using the Account Control API?
To get started using the Account Control API, please contact a Wasabi Sales Representative at email@example.com.
4. Where can I find the API guide?
5. What is the relationship between my Wasabi Account, and accounts created with the Account Control API?
Your Wasabi Account will become the Control Account that is associated with billing. Accounts created on the Account Control API are considered “Sub-Accounts” that are related to your “Control Account”. Sub-Accounts are Wasabi storage accounts whose administration (billing, password resets, etc.) is managed by you.
6. How am I billed when using the Account Control API?
When using the Account Control API, you are billed as you normally would be, via 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.
7. How are consumers billed when created with the 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.
8. How can I determine the amount of storage used by consumers?
In order to return the daily storage and data transfer associated with the sub-account, across all buckets in the Sub-Account by using:
Using from and to query string parameters (in the format YYYY-MM-DD) will apply date filters to the result set.
9. Can I migrate an existing Wasabi Account to an account created with the Account Control API?
No, there is no way to migrate an existing Wasabi Account to an account created with the Account Control API. All accounts available via the API must be newly created there.
10. Can I migrate data from an existing Wasabi Account to a new account created with the Account Control API?
Yes, you can migrate data from an existing Wasabi Account to a new account created with the Account Control API. However, the only way to migrate data is by using Wasabi Explorer or another 3rd Party Transfer Application.
11. What’s the difference between Wasabi Account Control API Key and S3 API Key?
Wasabi Account Control API keys are a unique keyset of primary & secondary keys which are only used to create and manage your Wasabi Account Control API implementation. Each Wasabi account does not necessarily gain access to Wasabi Account Control API keyset.
S3 API Keys are a unique keyset of Active & Secret keys which are only used to manage your storage account. Each Wasabi account is entitled for a minimum of One pair of S3 keys.
12. What’s the difference between Primary & Secondary Wasabi Account Control API key?
Primary & Secondary API keys provided by Wasabi are no different in its entitlement. Either of the keys can be used for Wasabi Account Management API implementation.
13. 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?
A 'Control' Wasabi account is no different to a Sub-Account from a storage perspective. Control Accounts will NOT display the sub-accounts created via the Wasabi Account Control API interface. Only way to list all the sub-accounts created is by performing GET /v1/accounts operation via your existing Wasabi Account Control API implementation.
14. How do I see account information for a specific Sub-Account?
In order 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.
15. What happens if i choose to cancel my Wasabi Account Control API subscription?
Wasabi Account Control API subscription can be canceled at anytime.
- What happens to my existing sub-accounts when i cancel subscription?
At cancellation, Account Control API keys are not valid anymore. Any sub-accounts that were created while subscription was active, those sub-accounts will continue to operate as before, however control account will lose the ability to manage (update, delete, reset S3 API keys & more) all of the sub-accounts. That includes access to sub-invoice data as well.
- What is Wasabi's recommended approach to cancel WAC subscription?
Before canceling the WAC subscription, consider deleting all sub-accounts, 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, that includes sub-users, access keys, IAM policies etc