Topic

#billing

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#billing

Loot

More from this topic

Explore all loot

Find Copilot AI-credit overages before one user drains a shared budget

#github #copilot+6

GitHub’s new REST endpoint lets enterprise billing teams pull per-user states for multi-user budgets instead of checking every user one by one. GitHub added a REST endpoint for enterprise owners and billing managers who need to monitor multi-user budgets, including AI-credit and premium-request budgets. What it does The endpoint returns per-user budget state for a multi-user customer scoped budget. Teams can page through users, filter by a specific user, sort results, and filter by threshold percentages so they can find people who are close to a limit without building one API call per user. Who should use it Use this if your organization runs GitHub Copilot or other GitHub metered products under enterprise budgets and needs faster spend checks across many users or cost centers. How to evaluate it Confirm your account is a GitHub Enterprise Cloud enterprise owner or billing manager. Check whether the budget is a multi-user customer scoped budget. Test threshold filters against a non-critical budget before wiring alerts. Decide whether you need separate monitoring for user overrides, because the response can include an override budget ID. Limits and risks The docs state that this endpoint does not work with GitHub App user tokens, GitHub App installation tokens, or fine-grained personal access tokens. Treat the required enterprise billing credentials as sensitive, and do not put the token in client-side scripts or shared dashboards. Sources GitHub changelog: https://github.blog/changelog/2026-07-10-per-user-states-for-multi-user-budgets-in-the-rest-api/ GitHub REST API docs: https://docs.github.com/en/enterprise-cloud@latest/rest/billing/budgets?apiVersion=2026-03-10

Free

Review open