GitHub adds direct cost-center lookup to its REST API
GitHub announced on November 3 that its REST API can now look up which cost center a user, organization, repository or enterprise team belongs to. The change adds a direct membership lookup for billing administration. It is not a change to the price of GitHub Copilot or another GitHub service.
Previously, administrators had to list every cost center and scan its resources to find the association, according to GitHub. The new endpoint accepts the resource type and name, allowing a caller to request that association directly rather than reconstructing it from all cost centers.
The response includes the cost center's ID and name. When the resource does not belong to a cost center, the memberships array is empty. An empty membership result should not be presented as proof that the resource has no usage charges.
Enterprise owners, billing managers and GitHub Apps with read access to enterprise billing can look up any resource in the enterprise. The announcement describes role-based access to this lookup; it does not grant new billing permissions to everyone who can access a repository.
Organization owners and users with custom roles that include enterprise-billing read access have a narrower view. GitHub says they can look up only the resources and cost centers they can already see. A direct lookup therefore does not bypass existing visibility restrictions.
Teams connecting GitHub billing data to internal reporting can use the endpoint to find a resource's existing cost-center association. The announcement does not claim an automatic accounting integration, a measured reduction in reporting latency or a new spending cap. It also does not say that this lookup changes cost-center assignments.