Registry API
Workspaces
Create workspaces, update them, roll them back and read their rendered output.
A workspace is the desired state for one repository or home directory. Every update increases its revision; rollback returns it to an earlier one.
The rendered and preview operations return the files the workspace renders, the same output `wl pull` produces, and the drift operation returns the drift reports recorded for it.
Operations
| Request | What it does |
|---|---|
| GET /api/v1/workspaces | List workspaces |
| POST /api/v1/workspaces | Create a workspace |
| GET /api/v1/workspaces/templates | List workspace templates |
| POST /api/v1/workspaces/from-template | Create workspace from template |
| GET /api/v1/workspaces/{id} | Get workspace manifest |
| PATCH /api/v1/workspaces/{id} | Update workspace config |
| GET /api/v1/workspaces/{id}/revisions | List workspace revisions |
| POST /api/v1/workspaces/{id}/rollback | Rollback workspace to a revision |
| GET /api/v1/workspaces/{id}/drift | Get workspace drift reports |
| GET /api/v1/workspaces/{id}/rendered | Get rendered workspace output |
| GET /api/v1/workspaces/{id}/preview | Preview rendered workspace output (CLI parity) |
Paths and summaries come from apps/api/openapi.json, which CI regenerates from the route definitions; this site checks its list against that file. Only the Public operations work without a token; everything else needs a signed-in session or an API token.