GitHub adds REST API access to per-user budget states for enterprises

GitHub has added a REST API endpoint that lets Enterprise Cloud administrators retrieve per-user consumption states for multi-user budgets from one place, a small but useful change for organizations trying to govern AI and platform spending at scale.

The July 10 GitHub Changelog post says enterprise owners and billing managers can now page through every user's progress against a multi-user budget, including the amount consumed and the allocated limit. The endpoint also supports filters for usage percentage, a single user lookup, sorting by consumption, and visibility into individual budget overrides.

Why it matters

GitHub has been expanding cost-center and budget controls as more developer workflows move into metered products such as Copilot and other enterprise services. In large companies, a single budget can apply across many teams or every user in an enterprise. Before this update, GitHub says teams had to make one API call per user to inspect consumption and could not filter directly by how much of the budget had already been used.

That made budget review a scripting problem for finance operations, platform engineering, and developer productivity teams. A central endpoint changes the workflow: administrators can request a page of users, sort or filter for people near a threshold, and identify accounts that need attention without walking the enterprise user by user.

What changed

• The endpoint reports each user's consumed amount and allocated limit for a selected multi-user budget.
• It can filter users by percentage of budget consumed, making threshold-based reviews easier.
• It can sort results by consumption and show when a user has an individual override.
• GitHub says it works for universal enterprise budgets and per-user budgets scoped to a cost center.

The release is aimed at GitHub Enterprise Cloud customers rather than individual developers. Still, it reflects a broader shift in software tooling: AI-assisted development, code scanning, and cloud-hosted automation are increasingly managed as measurable enterprise resources, not just features that get switched on globally.

For teams already watching Copilot or platform usage closely, the immediate value is operational. The new API should make it easier to build budget dashboards, alerts, or scheduled reports that highlight users approaching their limits before surprise overages or blocked work appear. GitHub points administrators to the REST API documentation for implementation details.

Sources

• github.blog

Cover photo by Lukas Blazek on Pexels, used under the Pexels License.