Get the effective organization plan

GET/v1/billing/organization/plan

Resolves the canonical organization subscription, legacy compatibility source, entitlements, and usage controls.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Effective organization planapplication/json
FieldTypeRequiredDescription
organizationIdstringNo—
planIdsandbox | builder | team | enterpriseNo—
planobjectNo—
plan.idsandbox | builder | team | enterpriseYesUnique identifier.
plan.namestringYesHuman-readable name.
plan.audiencestringNo—
plan.descriptionstringNoHuman-readable description.
plan.priceobjectYes—
plan.includedUsageUsdnumberYes—
plan.includedUsageCadenceone_time | monthly | commitmentNo—
plan.includedBuilderSeatsintegerNo—
plan.includedOperatorSeatsintegerNo—
plan.defaultMonthlyOverageLimitUsdnumberNo—
plan.selfServebooleanNo—
plan.featuresstring[]No—
plan.entitlementsobjectYes—
sourceorganization_subscription | legacy_owner_subscription | sandbox_defaultNo—
subscriptionobjectNo—
builderSeatsobjectNo—
builderSeats.capacityintegerYes—
builderSeats.activeintegerYes—
builderSeats.reservedintegerYes—
builderSeats.allocatedintegerYes—
builderSeats.availableintegerYes—
controlsobjectNo—
controls.overageEnabledbooleanNo—
controls.monthlyOverageLimitUsdnumberNo—
catalogVersionstringNo—
Get the effective organization plan
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow