No detailed documentaion about "plan" object in GET Organization Details API endpoint

[Aakash4792]

Select Topic Area

Question

Body

I am using GitHub EMU. I would like to know how many members in my organization are currently consuming licenses. I do see this "plan" object in the GET Organization Details API endpoint, but I dont understand what each of the fields mean and which one exactly corresponds to the count of people in the organization currently consuming licenses.

API being used: https://docs.github.com/en/rest/orgs/orgs?apiVersion=2022-11-28#get-an-organization
URL: https://api.github.com/orgs/ORG

[Ariel-Canseco]

When using GitHub Enterprise Managed Users (EMU), license consumption is not directly derived from the plan object returned by the GET /orgs/{org} endpoint.

The plan object typically includes fields like:

name

space

private_repos

collaborators

filled_seats

seats

However, in Enterprise environments (including EMU), the plan object is often legacy information and does not reliably represent active license consumption.

🔎 How License Consumption Works in EMU

For Enterprise Managed Users, licenses are consumed at the Enterprise account level, not strictly at the organization level.

A license is considered consumed when:

A managed user account exists within the enterprise.

The user is provisioned via your IdP (SCIM).

The account is active (not suspended).

How to Get Accurate License Usage:

Instead of relying on the plan object, you should:

Use the Enterprise-level API:

GET /enterprises/{enterprise}/consumed-licenses
OR
GET /enterprises/{enterprise}/license

Or check directly in:
Enterprise Settings → Billing → Licenses

This will give you:

Total licenses purchased

Licenses consumed

Available seats

⚠ Important Clarification

The filled_seats field in the plan object may reflect seats for legacy organization plans, but it does not accurately represent license usage in EMU environments.

In EMU:

Licenses are managed centrally at the Enterprise level.

Organization membership alone does not define license consumption.

Managed user provisioning determines license allocation.

Summary

If you're using EMU, you should query Enterprise billing or license endpoints rather than relying on the plan object in the organization API response.