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

# List usage quotas

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

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/usage/quotas/{quota_namespace}`
- 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`
- TypeScript: <https://skmtc.dev/datadog/apis/datadog-api-v2-collection/docs/api/v2/usage/quotas/:quota_namespace/get.ts> (a function with typed inputs; its response is checked against the schema)

Lists usage quotas for the caller's organization in a quota namespace. You can optionally include
descendant organizations in the same datacenter as the caller. Requires the `billing_read` or
`billing_edit` permission.

## Path parameters

- `quota_namespace` string, required

## Query parameters

- `include_descendants` boolean
- `page[cursor]` string
- `page[limit]` integer

## Response `200`

OK

- UsageQuotasListResponse: Response containing a paginated list of usage quotas.
  - `data` UsageQuotaResponseData[], required: A list of usage quota resources.
    - `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.
  - `meta` UsageQuotasResponseMeta, required: Pagination metadata for a usage quota list response.
    - `page` UsageQuotasResponseMetaPage, required: Cursor pagination fields for a usage quota list response.
      - `next_cursor` string: An opaque cursor for retrieving the next page. Omitted when there are no more results.

## Other responses

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

---

[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/3f70db624329?raw)