Database endpoints
Read usage and limits
Returns the tenant's configuration, limits and live usage counters.
GET /v1/tenants/{tenant}/usage
- Request tenant usageRead configuration, limits and live counters.
- Compare units and scopeSeparate overall used counters from per-table usage.
- Plan from known capacityInterpret each limit using its reported unit.
Before you start
Use your database bearer token.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
used contains current counters and schemas contains per-table usage. Read each value with its unit; a null capacity value is unknown here, not an unlimited allowance.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 429 | Honor Retry-After when present; back off. |
| 502 | Check service availability and the write outcome. |
| 503 | Honor Retry-After when present; check write outcomes. |