The Wasabi Account Control API (WACA) is a RESTful JSON API for programmatically managing Wasabi Sub-Accounts under a Control Account. Use it to create Sub-Accounts, generate S3 access keys for them, query usage and invoices, and convert trials to paying accounts.
WACA is a Wasabi-specific API. It is not part of, and not compatible with, any AWS API of similar name or purpose.
Base URL
https://partner.wasabisys.comAll requests must use HTTPS.
Quick Start
Once Wasabi Account Control API access is enabled on your Control Account and you have generated an API key:
curl -H "Authorization: $WACA_API_KEY" \
https://partner.wasabisys.com/v1/accountsA 200 response listing your Sub-Accounts confirms the API is reachable and your key works. See Authentication for the full auth flow.
What You Can Do With This API
Create a new Sub-Account linked to your Control Account
Generate S3 access keys for Sub-Accounts
Manage Sub-Account trial parameters (extend trial period, change quotas)
Convert a Sub-Account trial to a full paying account
Query usage of Sub-Accounts at the account and bucket level
Retrieve invoices for Sub-Accounts
Delete Sub-Accounts
Manage account profile information (email, etc.)
For request and response examples on every endpoint, see the Wasabi Partner API Reference or the Wasabi Postman collection.
Getting Started
To use the Wasabi Account Control API, you need:
A Wasabi Control Account out of trial and tied to a payment method.
Wasabi Account Control API access enabled on that Control Account — contact Wasabi Sales to request access.
A Wasabi Account Control API key — see Generating a Wasabi Account Control API Key.
The Control Account holder is responsible for all actions taken through the API, including any resulting service charges and security obligations. Wasabi reserves the right to suspend API access in cases of misuse.
WACA vs. WACM
WACA is the API. Wasabi Account Control Manager (WACM) is the hosted graphical interface built on top of it. If you want a ready-made UI for managing Sub-Accounts, use WACM. If you need to integrate Sub-Account management into your own platform, use WACA directly.
Reference
Authentication — auth header, examples, error codes
Generating a Wasabi Account Control API Key — UI walkthrough
Rate Limiting — per-method request limits
Billing and Utilization — billing model and usage metric definitions
Setup, Limits, and Policies — account prerequisites and Wasabi-branded email behavior
FAQs — common questions
Wasabi Partner API Reference — per-endpoint examples
Support
Contact Wasabi Customer Support for questions about WACA, including reporting issues and requesting features.