---
title: "Get all budgets for an organization"
method: GET
path: "/organizations/{org}/settings/billing/budgets"
tags: ["billing"]
---

# Get all budgets for an organization

`GET /organizations/{org}/settings/billing/budgets`

Gets all budgets for an organization. The authenticated user must be an organization admin or billing manager.
Each page returns up to 100 budgets.

## Path parameters

- `org` string, required

## Query parameters

- `page` integer
- `per_page` integer
- `scope` 'enterprise' | 'organization' | 'repository' | 'cost_center' | 'multi_user_customer' | 'user'
- `user` string

## Response `200`

Response when getting all budgets

- GetAllBudgets
  - `budgets` Budget[], required — Array of budget objects for the enterprise
    - `id` string, required — The unique identifier for the budget
    - `budget_type` union, required — The type of pricing for the budget
      - 'SkuPricing'
      - 'ProductPricing'
    - `budget_amount` integer, required — The budget amount limit in whole dollars. For license-based products, this represents the number of licenses.
    - `prevent_further_usage` boolean, required — The type of limit enforcement for the budget
    - `budget_scope` 'enterprise' | 'organization' | 'repository' | 'cost_center' | 'multi_user_customer' | 'multi_user_cost_center' | 'user', required — The scope of the budget
    - `budget_entity_name` string — The name of the entity for the budget (enterprise does not require a name).
    - `user` string — The user login when the budget is scoped to a single user (`user` scope).
    - `consumed_amount` number — The amount consumed for a user-scoped budget, or for a multi-user budget when filtering by user.
    - `budget_product_sku` string, required — A single product or sku to apply the budget to.
    - `budget_alerting` object, required
      - `will_alert` boolean, required — Whether alerts are enabled for this budget. Ignored for user-scope as alerting is disabled for them.
      - `alert_recipients` string[], required — Array of user login names who will receive alerts. Ignored for user-scope as alerting is disabled for them.
    - `expires_at` string, date — The date the budget will expire in `YYYY-MM-DD` format. Only dates in the future are accepted. If not provided, the budget will not expire. Only supported for budgets with `budget_scope` of `user`
  - `user` string — User login included when the response is scoped with the `user` query parameter.
  - `effective_budget` object — Effective user-level budget details returned when the response is scoped with the `user` query parameter.
    - `id` string, required — The unique identifier of the effective budget.
    - `budget_amount` integer, required — The budget amount for the effective budget.
    - `consumed_amount` number, required — The consumed amount for the specified user within the effective budget.
  - `has_next_page` boolean — Indicates if there are more pages of results available (maps to hasNextPage from billing platform)
  - `total_count` integer — Total number of budgets matching the query

## Other responses

- `403` — Forbidden
- `404` — Resource not found
- `500` — Internal Error

## Changes

> 62 revisions in range; 1 not diffed, 8 could not be searched.

- **2026-06-30** (2022-11-28) `36fd7551a71b` — 1 warning
  - added the new `multi_user_cost_center` enum value to the `budgets/items/budget_scope` response property for the response status `200`
- **2026-06-03** (2022-11-28) `b3f4b4706b41` — 6 warning, 6 info
  - added the new `cost_center` enum value to the `budgets/items/budget_scope` response property for the response status `200`
  - added the new `enterprise` enum value to the `budgets/items/budget_scope` response property for the response status `200`
  - added the new `multi_user_customer` enum value to the `budgets/items/budget_scope` response property for the response status `200`
  - added the new `organization` enum value to the `budgets/items/budget_scope` response property for the response status `200`
  - …8 more
- **2026-03-10** (2022-11-28) `5607301d0482` — 2 breaking, 2 info
  - added `subschema #1, subschema #2` to the `budgets/items/budget_type` response property `oneOf` list for the response status `200`
  - the `budgets/items/budget_type` response's property type/format changed from `string`/`` to ``/`` for status `200`
  - removed the `ProductPricing` enum value from the `budgets/items/budget_type` response property for the response status `200`
  - removed the `SkuPricing` enum value from the `budgets/items/budget_type` response property for the response status `200`

[Change history](https://skmtc.dev/github/apis/rest/changes/organizations/:org/settings/billing/budgets/get.md)

---

[API](https://skmtc.dev/github/apis/rest.md) · [All operations](https://skmtc.dev/github/apis/rest/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/github/rest/revisions/5bded2c77b93/schema)