GitHub Apps can now be granted an enterprise billing permission, available as read or read-and-write, on GitHub Enterprise Cloud. This lets an app installation access token call the enterprise billing REST API to pull usage data, reconcile invoices, and manage budgets and cost centers, replacing reliance on a personal access token from an enterprise owner or billing manager. App tokens also come with higher rate limits than personal access tokens.
Questions this post answers
How can I access GitHub Enterprise Cloud billing data through the API without using a personal access token?
Grant a GitHub App the enterprise billing permission, available as read-only or read and write, when creating or configuring the app. The resulting app installation access token can call the enterprise billing REST API endpoints to pull usage data, reconcile invoices, and manage budgets and cost centers, and it also gets higher rate limits than a personal access token. This permission is available on GitHub Enterprise Cloud. daily.dev helps engineers track GitHub platform changes like this before automation breaks.
Why did my GitHub billing automation break when an employee left or changed roles?
Billing automation tied to a personal access token from an enterprise owner or billing manager breaks when that individual's token becomes invalid, such as after they change roles or leave the company. GitHub now lets enterprise owners grant a GitHub App the enterprise billing permission instead, so an app installation token, not a person's token, powers the automation. daily.dev keeps teams current on GitHub changes that affect billing and access reliability.