Get a usage quota
Changed onReturns a usage quota's current configuration by its opaque identifier. Scheduled limits are returned separately until they take effect, after which they are returned as the current limit.
By default, you can retrieve quotas from your organization and authorized descendant organizations in the same data center. Set include_descendants=false to restrict access to your organization.
A quota remains readable after its associated user, role, or team is deleted. Requires billing_read or billing_edit.
Request
- Base URLhttps://api.datadoghq.com
- Auth
- API key in header DD-API-KEY and API key in header DD-APPLICATION-KEY
- or OAuth 2Authorization code/oauth2/v1/authorizeToken URL/oauth2/v1/tokenScopesbilling_read
- or OAuth 2Authorization code/oauth2/v1/authorizeToken URL/oauth2/v1/tokenScopesbilling_edit
Path parameters
The product-specific namespace whose usage quotas are being managed.
The opaque quota identifier returned by a previous list or create request. Clients must pass this value verbatim.
Query parameters
Allow access to authorized descendant organizations in the same data center. When false, an identifier belonging to any other organization returns 403. Defaults to true for ID-based operations to preserve existing descendant access.
Response
OK
Example response
{
"data": {
"attributes": {
"enforced": true,
"org_public_id": "abcdef12345",
"pending_effective_from": "2026-11",
"pending_usage_limit": 50000,
"scope": {
"user_handle": "jane@example.com"
},
"usage_limit": 100000
},
"id": "MTIzNB9haV9jcmVkaXRzH3VzZXJfaGFuZGxlOl9fQUxMX18",
"type": "quotas"
}
}Changes
- info
the security scope
billing_readwas added to the endpoint's security schemeAuthZ - info
the security scope
billing_editwas removed from the endpoint's security schemeAuthZ
- info
- info
the security scope
billing_readwas added to the endpoint's security schemeAuthZ - info
the security scope
billing_editwas removed from the endpoint's security schemeAuthZ
- info