Per-user states for multi-user budgets in the REST API

Дата публикации: 10-07-2026 15:07:23

You can now retrieve every user’s progress against a multi-user budget from a single REST API endpoint. This makes it much faster to find who is close to their limit…
The post Per-user states for multi-user budgets in the REST API appeared first on The GitHub Blog.

Основное содержимое страницы с новостью.

You can now retrieve every user’s progress against a multi-user budget from a single REST API endpoint. This makes it much faster to find who is close to their limit across a large enterprise.

Previously, you had to make one API call per user to check per-user consumption, and you couldn’t filter by how much of the budget someone had used. Reviewing spend across a large budget was slow and pushed teams to build their own scripts. Now you can page through all users from one endpoint and go straight to the people who need attention.

With this endpoint, you can:

• Get how much each user has consumed and their allocated limit for a multi-user budget, one page at a time.
• Filter by how much of the budget each user has used, so you can pull everyone at or above a certain percentage of their limit in one request.
• Filter to a single user or sort the results by how much of the budget each person has consumed.
• See when a user has an individual budget override that changes the limit applied to them.

This works for both types of multi-user budget: a universal budget that applies to every user in your enterprise and a per-user budget scoped to a cost center.

Who can use this

Enterprise owners and billing managers on GitHub Enterprise Cloud can call this endpoint for any multi-user budget in their enterprise.

To learn more, see Get user states for a multi-user budget in the REST API documentation.

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	New pull requests dashboard is now generally available	5	7	09-07-2026
2	GitHub Mobile: Improved filters and sorting for Copilot sessions	0	5	10-07-2026
3	Organization-level targeting for GitHub Code Quality	5	7	09-07-2026
4	Ask Copilot for a repository overview	0	5	09-07-2026
5	Clearer names for secret scanning detector types	0	3	10-07-2026
6	Как ограничить расходы на OpenAI API, чтобы ИИ-агенты не сожгли бюджет	0	8	04-07-2026
7	CodeQL 2.26.0 adds Kotlin 2.4.0 support and AI prompt injection detection	5	7	10-07-2026
8	General API errors	0	5	28-03-2026
9	Минфин обеспечит "полную прослеживаемость" трат на нацпроекты	0	0	03-10-2019
10	Increased API Errors	0	5	08-05-2026

Классификация: Пресс-релизы. Схожих патентов: 0. Схожих новостей: 10. Тональность: 5. Информативность: 7. Источник: github.blog.