---
title: "Get a usage quota"
method: GET
path: "/api/v2/usage/quotas/{quota_namespace}/{id}"
tags: ["Usage Metering"]
---

# Get a usage quota

`GET /api/v2/usage/quotas/{quota_namespace}/{id}`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/usage/quotas/{quota_namespace}/{id}`
- Auth: one of:
  - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token` scopes: `billing_read`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token` scopes: `billing_edit`

Returns 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`.

## Path parameters

- `quota_namespace` string, required
- `id` string, required

## Query parameters

- `include_descendants` boolean

## Response `200`

OK

- UsageQuotaResponse: Response containing a usage quota.
  - `data` UsageQuotaResponseData, required: A usage quota resource.
    - `attributes` UsageQuotaResponseAttributes, required: Attributes of a usage quota.
      - `enforced` boolean, required: Whether usage above the limit is actively blocked instead of only tracked or alerted on.
      - `org_public_id` string, required: The public ID of the organization that owns the quota.
      - `pending_effective_from` string: The future UTC month when the scheduled limit takes effect, formatted as `YYYY-MM`, starting at 00:00 UTC on its first day. Present only together with `pending_usage_limit` and omitted when no change is scheduled.
      - `pending_usage_limit` number, double: The usage limit scheduled for the organization-wide quota in the usage units defined by the quota namespace. A value of `0` is valid. At the start of the effective month, this value becomes `usage_limit` and both pending fields are omitted. Omitted when no change is scheduled.
      - `scope` UsageQuotaResponseScope: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A `user_handle` value of `"*"` identifies the default quota applied to users without a specific quota. This field is omitted for an organization-wide quota.
      - `usage_limit` number, double, required: The quota limit in the usage units defined by the quota namespace. May be fractional for quotas configured before public writes required whole units.
    - `id` string, required: An opaque usage quota identifier. Clients must pass this value back verbatim in update and delete requests and must not infer any structure from it.
    - `type` 'quotas', required: The JSON:API resource type for a usage quota.

## Other responses

- `400`: Bad Request
- `403`: Forbidden
- `404`: Not Found
- `429`: Too many requests

## Changes

- **2026-11-13** `14d85160bfa9`: 2 info
  - the security scope `billing_read` was added to the endpoint's security scheme `AuthZ`
  - the security scope `billing_edit` was removed from the endpoint's security scheme `AuthZ`
- **2026-11-13** `021e91f3533e`: 2 info
  - the security scope `billing_read` was added to the endpoint's security scheme `AuthZ`
  - the security scope `billing_edit` was removed from the endpoint's security scheme `AuthZ`
- **2026-11-13** `ae8aa09476b9`: 2 info
  - the security scope `billing_read` was added to the endpoint's security scheme `AuthZ`
  - the security scope `billing_edit` was removed from the endpoint's security scheme `AuthZ`
- **2026-11-13** `af6fab7deae8`: 2 info
  - the security scope `billing_read` was added to the endpoint's security scheme `AuthZ`
  - the security scope `billing_edit` was removed from the endpoint's security scheme `AuthZ`
- **2026-11-13** `8156b595322c`: 2 info
  - the security scope `billing_read` was added to the endpoint's security scheme `AuthZ`
  - the security scope `billing_edit` was removed from the endpoint's security scheme `AuthZ`

[Operation history](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/changes/api/v2/usage/quotas/:quota_namespace/:id/get.md)

---

[API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/14d85160bfa9?raw)
