API reference · Account and billing
Quotas
1 operation of the Ankra Cloud API: Account quotas.
The account's limits and what it holds#
GET
/v1/quotas- Operation
get_quotas- Credentials
- API token, Portal session
- Requires
- Permission
read
Responses
200Limits and usage.application/json · Quota
| Field | Type | Description |
|---|---|---|
limitsrequired | QuotaAmounts | |
serversrequired | integer | |
coresrequired | integer | |
storage_gibibytesrequired | integer | |
floating_ipsrequired | integer | |
routersrequired | integer | |
private_networksrequired | integer | |
usagerequired | QuotaAmounts | |
serversrequired | integer | |
coresrequired | integer | |
storage_gibibytesrequired | integer | |
floating_ipsrequired | integer | |
routersrequired | integer | |
private_networksrequired | integer |
- 401Not signed in, or the credential is invalid or expired.
- 403The role lacks the permission, the token is read-only (a read-only token also gets
reason: read_only_token_cannot_read_credentialson every credential read), the CSRF header is missing, a support session may not do this, or the route needs a verified email address and the caller's is not (reason: email_unverified). - defaultAny other error, usually 500.
Example
curl 'https://cloud.ankra.app/v1/quotas' \
-H "Authorization: Bearer $ANKRA_CLOUD_TOKEN"