Verify organization checkout access
GET
/v1/billing/organization/checkout-contextConfirms that the authenticated organization owner, admin, or billing member may start a subscription or top-up checkout.
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.
200Checkout is permitted for the active organizationapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| organizationId | string | Yes | — |
| organizationName | string | Yes | — |
| organizationType | personal | company | No | — |
| role | string | Yes | — |
| canCheckout | true | Yes | — |
| planId | sandbox | builder | team | business | enterprise | No | — |
| builderSeats | object | No | — |
| builderSeats.capacity | integer | Yes | — |
| builderSeats.active | integer | Yes | — |
| builderSeats.reserved | integer | Yes | — |
| builderSeats.allocated | integer | Yes | — |
| builderSeats.available | integer | Yes | — |
| subscription | object | No | — |
403The actor cannot manage billing for this organization
None.
Verify organization checkout access
Loading...
Response 200
Loading...