• 24 Apr 2023
  • PDF


  • PDF

Article Summary

FAQs pertaining to the Wasabi Account Control API (WACA) are:

What is the relationship between my Wasabi account and an account created with WACA?

Your Wasabi account will become the Control Account that is associated with billing. Accounts created on WACA are considered sub-accounts that are 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 WACA?

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).

How are consumers billed when created with WACA?

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>/utilizations

Using from and to query string parameters (in the format YYYY-MM-DD) will apply date filters to the result set.

Can I migrate an existing Wasabi Account to an account created with WACA?

No. There is no way to migrate an existing Wasabi account to an account created with WACA. All accounts available via the API must be newly created there. 

Can I migrate data from an existing Wasabi account to a new account created with WACA?

Yes. You can migrate data from an existing Wasabi account to a new account created with WACA. However, the only way to migrate data is by using Wasabi Explorer or another Third Party Transfer Application.

What is the difference between a WACA Key and an S3 API Key?

WACA keys are a unique keyset of primary and secondary keys that are used only to create and manage your WACA implementation. Each Wasabi account does not necessarily gain access to WACA 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 for a minimum of one pair of S3 keys.  

What is the difference between a primary and secondary WACA key?

Primary and secondary API keys provided by Wasabi are not different in entitlement. Either of the keys can be used for WACA implementation.

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 WACA interface. The only way to list all the sub-accounts created is by performing a GET /v1/accounts operation via your existing WACA 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 WACA subscription?

A WACA subscription can be canceled at anytime.

What happens to my existing sub-accounts when I cancel 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 WACA subscription?

Before canceling a WACA 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.

What's Next