GitHub REST API
GET /orgs/{id}/team/{id}/copilot/metrics endpoint removal
Stopped workingSubscribe to GitHub REST APIShare
Calls to GET /orgs/{id}/team/{id}/copilot/metrics on GitHub REST API stopped working on April 2, 2026.
Calls it hits
GET /orgs/{id}/team/{id}/copilot/metrics
What to use instead of these calls
Use the Copilot usage metrics endpoints (/orgs/{org}/copilot/metrics/reports/... and /enterprises/{enterprise}/copilot/metrics/reports/...), which return download links to NDJSON reports.
In GitHub REST API's words
The Copilot Metrics API will sunset on April 2nd, 2026.
Facts
- API
- GitHub REST API
api.github.com - Kind
- Endpoint removal
- Announced
- January 29, 2026
- Takes effect
- April 2, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against GitHub REST API's own pages
Questions
When does this change take effect?
Calls to GET /orgs/{id}/team/{id}/copilot/metrics on GitHub REST API stopped working on April 2, 2026.
What happens to calls after April 2, 2026?
They have failed since April 2, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from GitHub REST API 10
-
GET /enterprises/{id}/copilot/metricsEndpoint removal Stopped working -
GET /enterprises/{id}/team/{id}/copilot/metricsEndpoint removal Stopped working -
GET /orgs/{id}/copilot/metricsEndpoint removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working -
PATCH /orgs/{id}Parameter removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.