Closing down notice of legacy Copilot metrics APIs

[yoav-dagan]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

API

Body

according to this: https://github.blog/changelog/2026-01-29-closing-down-notice-of-legacy-copilot-metrics-apis/
the copilot metrics api endpoints were deprecated on April 2nd, but article still points to the same endpoint:

https://api.github.com/orgs/ORG/copilot/metrics

but this brings 404 error.

{
"message": "Not Found",
"documentation_url": "https://docs.github.com/rest",
"status": "404"
}

which endpoint should I use now to get the following columns?

column_name

DATE
COPILOT_IDE_CHAT
TOTAL_ACTIVE_USERS
COPILOT_DOTCOM_CHAT
TOTAL_ENGAGED_USERS
COPILOT_DOTCOM_PULL_REQUESTS
COPILOT_IDE_CODE_COMPLETIONS

Thanks in advanced!

[AviJxn]

You're running into this because the legacy Copilot metrics endpoints were fully deprecated, and the old URL now returns 404 (even if some docs or blog posts still reference it).

So you're not doing anything wrong it's that endpoint is no longer valid.

Right now, GitHub hasn’t provided a direct 1:1 replacement endpoint for all of those metrics in the same format. Instead, Copilot usage data is being moved toward:

1. Updated / newer APIs (limited availability)
   Some Copilot metrics are being exposed through newer APIs, but they may:

• Require specific permissions (enterprise/org level)
• Not yet cover all previous fields
• Be in preview or gradually rolled out

2. GitHub UI (current reliable source)
   For now, the most complete and reliable view of those metrics is:

• Organization settings → Copilot → Usage / Analytics

3. Possible alternatives
   Depending on what you need, you can:

• Use audit logs (for activity-level insights)
• Export data from the UI (if available)
• Combine with internal tracking if you're measuring adoption

About your specific fields:
Columns like TOTAL_ACTIVE_USERS, CODE_COMPLETIONS, etc. were part of the legacy metrics model, and there isn’t currently a public REST endpoint that exposes all of them in the same structure.

What you should do next:

• Avoid relying on the deprecated endpoint
• Check Copilot analytics in the GitHub UI
• Keep an eye on updated docs / changelog for new metrics APIs
• If this data is critical, consider opening a feature request or contacting GitHub support for roadmap clarity

A lot of people are hitting this exact issue after the deprecation.

[Gecko51]

The old /orgs/{org}/copilot/metrics endpoint was sunset on April 2, 2026 as part of the legacy API shutdown, so the 404 is expected behavior, not something wrong on your end.

The replacement is the new Copilot usage metrics API, which uses a different URL pattern:

GET /orgs/{ORG}/copilot/metrics/reports/organization-1-day
GET /orgs/{ORG}/copilot/metrics/reports/organization-28-day/latest

For per-user data (where TOTAL_ACTIVE_USERS and TOTAL_ENGAGED_USERS live):

GET /orgs/{ORG}/copilot/metrics/reports/users-1-day
GET /orgs/{ORG}/copilot/metrics/reports/users-28-day/latest

Token-wise, you need manage_billing:copilot or read:org scope. Classic PAT and fine-grained PAT both work, just make sure the right org-level permissions are set.

One thing to know before you remap your pipeline: the field names changed. The old columns like COPILOT_IDE_CODE_COMPLETIONS are now split out by language and model in the new schema, so you won't get a direct 1:1 match. The full response structure is in the docs at docs.github.com/en/rest/copilot/copilot-usage-metrics.

What are you feeding this data into? Happy to help with the field mapping once you've seen the new schema.l