Manage the family by API
Every family endpoint takes the primary workspace’s API key inX-API-KEY; there is no workspace header to set. A Ringg Space’s own key works only inside that Ringg Space; family endpoints refuse it, usually with 403 Sub-workspaces are not enabled for this workspace. If the primary’s key gets that 403, ask Ringg support to enable the feature for your primary workspace.
Two things to know before you parse responses:
- Money formats. The read endpoints and the concurrency endpoint return amounts as JSON numbers (
200000.0); the two allocation endpoints return decimal strings ("200000.00"). Parse both before doing arithmetic. In requests, amounts can be numbers or numeric strings; they are rounded to 2 decimals. - Agents inside a Ringg Space. There is no family endpoint for this: a Ringg Space is a normal workspace, so call Create agent with that Ringg Space’s own API key. The agent is invisible from the primary and from sibling Ringg Spaces.
PATCH /workspace/sub/{sub_workspace_id}/concurrency):