GitHub Copilot Usage Metrics

[sftong2000]

Select Topic Area

Question

Body

Hello Helpers, I have an existing Power BI report that source the CoPilot usage metrics from the GitHub Enterprise APIs. This is the source URL:
https://api.github.com/enterprises/<enterprise_name>/copilot/metrics

This report was actually grab from Akash here -- https://github.com/orgs/community/discussions/141071
Thank You Akash @Akash1134

I understand from GitHub recently that the Enterprise CoPilot Usage metrics above, would be sunset on 4/2/2026. The new metrics should be sourced from a new site new API according to this doc -- https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage-metrics

Which reference the API URL -- https://api.github.com//enterprises/{enterprise}/copilot/metrics/reports/enterprise-28-day/latest

1. Usage now cut from last 90 days to 28 days.
2. The new API would return report links instead of data in JSON format. See the new response below.

This is really a big pain as the format is completely different. I need to make new codes, and worse still the doc does NOT show what schema format is the "report-1" and "report-2".

Anyone has tried to get the new report and data ? I truly wish some new PBI report like @Akash1134 is handy again. Thank you guys.

"{
"download_links": [
"https://example.com/copilot-usage-report-1.json",
"https://example.com/copilot-usage-report-2.json"
],
"report_start_day": "2025-07-01",
"report_end_day": "2025-07-28"
}"

[midiakiasat]

The “report-*.json” behind download_links is NDJSON (newline-delimited JSON), not a single JSON array/object. GitHub documents the field schema in “Data available in Copilot usage metrics” → “API and export fields” (these fields are what you’ll see per line/record).
So the workflow is:

1. Call GET /enterprises/{enterprise}/copilot/metrics/reports/enterprise-28-day/latest → get download_links (signed URLs expire).
2. For each download_link, download the file, split by newline, parse each line as JSON → append/union across files and days (28-day window).
3. Build your Power BI model from those parsed records; don’t expect a stable “report-1 vs report-2” JSON schema, both are NDJSON exports using the documented fields.

[sftong2000]

Thank you @midiakiasat and @Yigtwxx .

So in this new format of API, after my P(BI report send the API endpoint Request "/enterprises/{enterprise}/copilot/metrics/reports/users-28-day/latest", 2 report links would be returned as seen below. The PBI report would then Request again at these 2 report links and receive 2 files downloaded to my PC ? I mean, the end product of this new API is 2 FILES in format NDJSON, no longer a cloud data returned in NDJSON, correct ?

Thank You again

"download_links": [
"https://example.com/copilot-usage-report-1.json",
"https://example.com/copilot-usage-report-2.json"
]

[midiakiasat]

No, you don’t have to “download 2 files to your PC”.

What the new endpoint does is:

1. Your PBI (Power Query) calls
   GET /enterprises/{enterprise}/copilot/metrics/reports/*-28-day/latest
   → GitHub returns download_links (pre-signed, time-limited URLs) instead of the data payload.

2. Your PBI then makes HTTP GET requests to each download_link and reads the response body (the report content). Power BI can ingest this directly as web content; saving to disk is optional and not required.

So yes: the “end product” of that API call is links to report blobs, not inline JSON. But the data is still retrieved over HTTP, your code just has to do the second fetch to the download_links.

Key operational detail: those links are signed and expire, so your refresh must always:

• call the “latest” endpoint first,
• then immediately fetch the links.

[Yigtwxx]

Hello

I completely understand the frustration with the new API structure; the transition can definitely be a bit confusing at first. The main reason you're running into this issue is that the new system returns the data in NDJSON (Newline-Delimited JSON) format instead of a standard JSON object or array. This means that inside report-1.json or report-2.json, each individual line represents an independent JSON object, rather than being enclosed in a single large array.

To seamlessly integrate this data back into your Power BI report, you can follow these steps:

1. First, make a request to the new API endpoint (/enterprises/{enterprise}/copilot/metrics/reports/enterprise-28-day/latest) to retrieve the temporary URLs from download_links.
2. When you download these files, standard JSON parsers will likely throw an error due to the format. In Power Query, when reading these files, you need to split the data line by line (split by newline) and process each line as a separate record.
3. If you prefer using scripts for data transformation in Power BI, Python and the Pandas library are fantastic alternatives for reading NDJSON. You can directly convert the data into a proper table (DataFrame) with a simple command like pandas.read_json('filename.json', lines=True).
4. The data schema within the files exactly matches what is specified in the "API and export fields" section of the GitHub documentation. Once you read and append all the report files together, you can turn your current 28-day data into a table that fits your old report structure.

I hope these steps make migrating your report much easier. If this helped you, please mark it as the answer