We’re expanding the organization-level Copilot Usage Metrics API to include a broader set of pull request activity, including creation volume, throughput and cycle time. This brings the org-level endpoints to parity with what was previously available only at the enterprise level.

What’s new

Organizations can now retrieve daily aggregated pull request activity and Copilot participation metrics directly from the org-level API, including:

  • Baseline pull request activity
    • Total pull requests created
    • Total pull requests reviewed
    • Total pull requests merged
    • Median time to merge (minutes)
  • Copilot participation on pull request throughput + review quality
    • Pull requests created by Copilot (Copilot coding agent)
    • Pull requests reviewed by Copilot (Copilot code review)
    • Total review suggestions and total applied suggestions
    • Copilot suggestions and Copilot applied suggestions
    • Copilot-created pull requests that were merged
    • Median time to merge for Copilot-created pull requests

Why this matters

With this update, teams can:

  • Standardize reporting at the org level.
  • Quantify Copilot’s impact on the pull request lifecycle, from pull request creation to merge.
  • Track not just suggestion volume but also applied suggestions as a signal of actionable feedback.
  • Improve visibility into non-IDE Copilot usage, including agent-created pull requests and Copilot-authored review activity.

Important notes

  • If your organization belongs to an enterprise, organization-level totals may not match enterprise totals. Users can belong to multiple organizations, so their usage can appear in more than one organization report, while enterprise reporting deduplicates users.
  • If you see the API report is empty for everything but pull request data, it likely means they don’t have any IDE usage, so only pull request data is available.
  • Repo/org transfers can split attribution. If a repository is transferred after a pull request is created (or reviewed) but before it’s merged, events can be attributed to different orgs (e.g., pull request created/reviewed may count under the original org, while pull request merged counts under the new org). If an organization is transferred to a new enterprise, events may be split at the enterprise level, but at the org level, attribution stays with the same org.

For more information on the new data field definitions, visit our documentation about Copilot usage metrics. Join the discussion within GitHub Community.