Registry API
Workspaces
Workspace desired state: targets, revisions, the manifest the CLI pulls, overrides and policies.
A workspace is the desired state for one repo, folder, service or key. Updating it creates the next workspace revision. The manifest operation is what `wl pull` fetches; overrides pin a package’s version constraint or release channel; policies hold keyed rules such as the lockfile policy.
Operations
| Request | What it does |
|---|---|
| GET /workspaces/ | List workspaces |
| POST /workspaces/ | Create a workspace |
| GET /workspaces/{id} | Get a workspace |
| PUT /workspaces/{id} | Update a workspace (new revision) |
| GET /workspaces/{id}/manifest | Get the workspace manifest |
| GET /workspaces/{id}/overrides/ | List workspace overrides |
| POST /workspaces/{id}/overrides/ | Add a workspace override |
| DELETE /workspaces/{id}/overrides/{overrideId} | Remove a workspace override |
| GET /workspaces/{id}/policies/ | Get workspace policies |
| PUT /workspaces/{id}/policies/ | Set workspace policies |
Paths come from the OpenAPI document that the API exports from its route definitions (CI fails if it is stale); this site checks its list against that file. The public registry search and package reads and the health checks work anonymously; most other operations need a signed-in session or an API key.