Setup, Limits, and Policies
To use the Wasabi Account Control API, you must contact a representative from Wasabi to request access to the Wasabi Account Control API program. To be eligible for access to the API, you must:
Have an established Wasabi account (hereafter referred to as a Control Account) that is tied to a payment method (that is, no longer in a trial period), such as a credit card or manual invoicing (if approved by your Wasabi Sales Representative)
Meet any requirements as established by your Wasabi Sales Representative
It is important to note that while using the Wasabi Account Control API, you may not delete the Control Account. Your Wasabi Sales Representative will work with you to determine what limits will be applied to your Wasabi Account Control API participation, in particular:
The maximum number of Sub-Accounts you will be allowed to create
The default and maximum length of the Sub-Account trial period
The default and maximum trial period storage quota (in GB)
Emails
Wasabi typically sends Wasabi-branded emails during the lifetime of an account, such as:
A warning email is sent when an account is nearing the trial storage quota limit
An email is sent when a trial storage quota limit is surpassed, and the account can no longer upload new objects
Warning emails when an account is reaching the end of a trial period
Notifications when account trials have expired (and at various points during the “offboarding” process until the account is deleted)
All emails are Wasabi-branded, and there is no option to co-brand or white label emails for API developers at this time. Therefore, as a user of the Wasabi Account Control API, you (Control Account holder) will receive notification emails on behalf of any Sub-Accounts. The body of the email will sufficiently indicate the Sub-Account on which the email notification is occurring.
Since Wasabi does not send notification emails to end users, Wasabi Control Account holders will be required to adequately notify end users of the above conditions. There is enough information in the Wasabi Account Control API to determine when the above thresholds are reached to properly communicate via your user interface (UI) or email notification system.
Test Environments
Wasabi will have a test environment for the Wasabi Account Control API available for development and testing purposes. The test environment will have API keys generated that are distinct from the live API keys.
The test environment, while generally stable, will not offer the same Service Level and Quality of Service as the Wasabi production environment. Therefore, users of the Wasabi Account Control API should expect some service disruptions of the test environment from time to time.
Given that the Wasabi production environment places limits (and billing responsibility) on the Control Account, please do not create test accounts on the production environment. Given the billing rules described above, all Sub-Accounts ultimately become paying accounts and the Wasabi Account Control API user will be charged for all accounts in the production environment. Therefore, only use the test environments for development and testing of the integration with the Wasabi Account Control API.