/api/v6/account/limitsSpending limits
Active spending limits for the account, by scope. Read-only.
Scope and limits
API key with the account capability granted
30 requests per minute
Active spending limits for the account, by scope. This is a read-only endpoint: limits are configured from the customer portal. Amounts carry 6 decimals and thresholds are the percentages at which an alert fires.
Sensitive financial data
The API key must have the account capability explicitly enabled. Access to all services does NOT grant it: it is granted separately, per key, from the customer portal (Developers → API keys). A key without the capability gets 403.
Responses
Active limits.
{
"success": true,
"data": {
"items": [
{
"scopeType": "org",
"scopeRef": "0",
"amount": "1000000.000000",
"period": "monthly",
"thresholds": [80, 95]
}
]
},
"meta": {
"requestId": "b9b1704baffab21150213c02fd853975",
"timestamp": "2026-06-02T19:43:59+00:00",
"responseTimeMs": 4.1
}
}Invalid or missing credentials.
The API key lacks the required capability, or the organization cannot run the request.
Request limit exceeded. Wait for Retry-After.
Possible errors
Codes this endpoint can return in error.code. The full detail lives in the catalog.
AUTH_REQUIREDNo Bearer token was sent, and every call requires one.401AUTH_INVALID_KEYThe API key is not recognized: wrong format, revoked or expired.401AUTH_SERVICE_NOT_ALLOWEDThe key is not allowed to use the service behind this endpoint.403ACCOUNT_NOT_ACTIVEYour organization is suspended or closed.403ACCOUNT_BLOCKEDA full block is active: every call is rejected.403ACCOUNT_CONFIG_NOT_FOUNDWe could not load the organization behind your key.403FORBIDDENGeneric 403: fallback when no `ACCOUNT_*` applies.429RATE_TPS_EXCEEDEDYou exceeded your organization quota for this endpoint.