Get the public billing catalog

GET/v1/billing/catalog

Returns the versioned organization plans, service entitlements, and metered usage prices.

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.

200Active public billing catalogapplication/json
FieldTypeRequiredDescription
versionstringYes
statusactiveNoCurrent lifecycle status.
currencyUSDYes
effectiveFromstringNo
moneyPrecisionmicro_usdNo
billingAccountScopeorganizationYes
plansobject[]Yes
plans[].idsandbox | builder | team | business | enterpriseYesUnique identifier.
plans[].namestringYesHuman-readable name.
plans[].audiencestringNo
plans[].descriptionstringNoHuman-readable description.
plans[].priceobjectYes
plans[].includedUsageUsdnumberYes
plans[].includedUsageCadenceone_time | monthly | commitmentNo
plans[].includedBuilderSeatsintegerNo
plans[].includedOperatorSeatsintegerNo
plans[].defaultMonthlyOverageLimitUsdnumberNo
plans[].selfServebooleanNo
plans[].featuresstring[]No
plans[].entitlementsobjectYes
topUpsobject[]Yes
topUps[].idstringYesUnique identifier.
topUps[].namestringYesHuman-readable name.
topUps[].priceUsdnumberYes
topUps[].creditsUsdnumberYes
topUps[].descriptionstringYesHuman-readable description.
metersobject[]Yes
Get the public billing catalog
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow