GitHub API Adds Direct Cost Center Lookup
GitHub has added a REST API capability that lets authorized users identify the cost center associated with a resource. The change removes the need to inspect every cost center individually.
Radwan AbdulhadiEditor and technology writer
A more direct billing lookup
GitHub has introduced a way to use its REST API to determine which cost center a resource belongs to. The lookup covers four resource types named in the company’s announcement: users, organizations, repositories, and enterprise teams. The change is aimed at making cost-center administration more direct for people managing billing information across an enterprise. Further details are available from GitHub Changelog in the original source material.
Before this capability was available, administrators had to list every cost center and scan the resources associated with each one to find a particular membership. GitHub’s new approach allows the caller to provide the resource type and name to a dedicated lookup endpoint instead. That changes the task from reviewing a complete collection to requesting the membership information for a known resource.
What the response contains
The response includes the cost center’s ID and name, giving administrators both an identifier and a human-readable label for the matching cost center. This can help distinguish cost centers with similar administrative roles or support systems that need to store a stable identifier alongside a display name.
GitHub also specifies how the API represents a resource that is not assigned to a cost center. In that case, the memberships array is empty. The response therefore provides an explicit result for the absence of a membership rather than requiring users to infer it from a failed search through the full list of cost centers.
Permissions determine visibility
The lookup is governed by the caller’s permissions within the enterprise. Enterprise owners and billing managers can use it to look up any resource in the enterprise. GitHub Apps with read access to enterprise billing can also perform lookups across the enterprise, according to the changelog.
Other users have a narrower scope. Organization owners and users with custom roles that include read access to enterprise billing can look up only the resources and cost centers they are already allowed to see. The API therefore does not expand visibility beyond the permissions attached to the account, role, or app making the request.
Relevant for enterprise administration
Cost centers provide an organizational way to associate resources with billing ownership, and the new lookup is particularly relevant when an administrator already knows the resource that needs to be checked. A repository, organization, user, or enterprise team can now serve as the starting point for finding its cost-center assignment.
The change may also simplify internal tools that need to answer resource-level billing questions. Instead of collecting all cost centers and searching their resource lists, those tools can use the resource’s type and name as the inputs to a focused request, subject to the permissions available to the integration or operator.
Documentation and availability
GitHub directs users to the REST API documentation for the operation titled Get cost center membership for a resource. The documentation is the appropriate reference for the request details and supported usage of the new lookup capability.
The announcement does not describe any changes to cost-center assignments themselves. Instead, it focuses on how authorized users and applications can retrieve membership information more efficiently. The central result is a narrower, resource-first lookup that returns the relevant cost-center identity when one exists and an empty memberships array when it does not.
Sources
- GitHub ChangelogLook up a resource’s cost center with the GitHub REST API
Continue chronologically
Related entity coverage
Related stories
GitHub Automates SSO Authorization for PATs and SSH Keys
GitHub Enterprise Cloud admins can now bulk-authorize classic PATs and SSH keys across up to 50 SSO-protected organizations.
GitHub Adds REST API Control for Code Coverage Rules
GitHub now lets teams manage the Restrict code coverage repository ruleset through its generally available REST API.
GitHub Copilot Gains Server-to-Server Authentication
GitHub Copilot now supports server-to-server authentication for organization-installed apps in public preview, enabling automated agent workflows.
GitHub Announces Major App Improvements for Least Privilege
GitHub releases new updates for GitHub Apps to improve least privilege access, streamline repository management, and help developers transition from classic PATs.
