Registry API
Workspaces
Create workspaces, manage their targets, packages and config, and read their revisions.
A workspace is the desired state an org distributes: targets, the packages assigned to them and config. Every change creates a revision. Preview renders a plan without writing anything, and config diff shows what a change would do.
Operations
| Request | What it does |
|---|---|
| POST /api/v1/workspaces | Create workspace |
| GET /api/v1/workspaces | List workspaces |
| GET /api/v1/workspaces/{id} | Get workspace detail |
| PATCH /api/v1/workspaces/{id} | Update workspace |
| GET /api/v1/workspaces/{id}/targets | List targets |
| POST /api/v1/workspaces/{id}/targets | Create target |
| DELETE /api/v1/workspaces/{id}/targets/{targetId} | Delete target |
| GET /api/v1/workspaces/{id}/revisions | List revisions |
| GET /api/v1/workspaces/{id}/config | Get workspace config |
| PUT /api/v1/workspaces/{id}/config | Update workspace config |
| GET /api/v1/workspaces/{id}/config/diff | Get config diff |
| POST /api/v1/workspaces/{id}/preview | Generate render preview |
| POST /api/v1/workspaces/{id}/packages | Add package |
Paths and summaries come from apps/api/openapi.json, which CI regenerates from the route definitions; this site checks its list against that file. Telemetry ingest accepts a workspace key without a user session; everything else needs a signed-in user.