List an External workspace's end users with their usage and caps
Needs billing.read. Every end user with usage in the workspace's projects this billing period, an override, or a notice, by machine-hours descending, with the cap that holds it and whether it reached it. An API key may call it; a key pinned to a workspace only for its own, and any other workspace answers it the same 404 as one that does not exist. An Internal workspace has no end users: every operation here answers it with 409 internal_workspace. Off until the workspace API is enabled for this deployment: until then it answers 404 to everyone.
Authorization
bearerAuth A RemoteHost API key (rh_sk_...) or a user session token.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/orgs/string/workspaces/string/end-users"{ "workspace": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "kind": "internal" }, "defaultMachineHourLimit": 0, "action": "refuse_new", "periodStartsAt": "string", "periodEndsAt": "string", "endUsers": [ { "endUserId": "string", "machineHours": 0, "estimatedCogsUsd": 0, "machineHourLimit": 0, "limitSource": "override", "status": "under", "reachedAt": "string" } ]}Set one end user's cap in an External workspace PUT
Needs `billing.manage`. Overrides the workspace's default for this end user; null exempts it. An Internal workspace has no end users: every operation here answers it with 409 `internal_workspace`. API keys cannot call it. Off until the workspace API is enabled for this deployment: until then it answers 404 to everyone.
Read a workspace's usage at vendor cost, itemized GET
Needs `billing.read` at the workspace. The usage of the projects in the workspace now, for the billing period, line by line at each vendor's own rate, with the usage fee and the platform fee, which are displayed for transparency: nothing bills them yet. A caller who cannot see the workspace (a member holding no project in it) gets the same 404 as a workspace that does not exist. An API key pinned to a workspace reads that workspace only, with `billing.read` in its own scopes; any other workspace, in this org or another, gets the same 404. No other API key may call it. Off until the workspace API is enabled for this deployment: until then it answers 404 to everyone.