API Methods - Endpoints

Overview

The following methods are the entirety of the Wasabi Account Control API v1 specification. Authentication is done via the standard Authorization HTTP Request Header. Callers should pass in the Wasabi Account Control API key for the value.

All methods will return a HTTP status code of 200 on success and a non-200 value for failure. For failures, a failure description will be returned in the JSON response.

For each method, sample request and response headers and bodies are included. Note that sensitive (or variable) information has been redacted from the samples with a [DELETED] tag.

Wasabi Account Control API requests: https://partner.wasabisys.com
Note that this link is used when requesting data; there is no application or page to access.

The following endpoints are described:

• GET /v1/accounts
• GET /v1/accounts/<AcctNum>
• GET /v1/accounts/<AcctNum>/utilizations
• GET /v1/accounts/<AcctNum>/utilizations/buckets
• GET /v1/accounts/<AcctNum>/utilizations/buckets/<BucketName>
• GET /v1/accounts/<AcctNum>/invoices
• GET /v1/accounts/<AcctNum>/invoices/<SubInvoiceNum>
• GET /v1/accounts/<AcctNum>/invoices/<SubInvoiceNum>/regional
• PUT /v1/accounts
• POST /v1/accounts/<AcctNum>
• DELETE /v1/accounts/<AcctNum>
• GET /v2/accounts
• GET /v2/accounts/<AcctNum>/invoices
• GET /v2/accounts/<AcctNum>/utilizations
• GET /v2/accounts/<AcctNum>/buckets/<BucketName>
• GET /v1/utilizations
• GET /v1/utilizations/buckets
• GET /v1/utilizations/status
• GET /v1/control-account
• GET /v1/control-account/utilizations
• GET /v1/control-account/utilizations/bucket
• GET /v1/control-account/bucket-utilizations