Registry API
API keys
Scoped bearer credentials for one user in one organization.
An API key is limited to its scopes, written verb:resource, with no admin super-scope. The token is returned once at creation and never listed again. `wl apikey` wraps these operations.
Operations
| Request | What it does |
|---|---|
| POST /api-keys/ | Create an API key (token shown once) |
| GET /api-keys/ | List API keys |
| DELETE /api-keys/{id} | Revoke an API key |
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.
More areas
All areas →- 01
Public registry and blobs
Anonymous search and package pages, plus content-addressed blob storage.
- 02
Packages
Create packages, publish immutable versions, manage assets, approvals, render previews and reviews.
- 03
Workspaces
Workspace desired state: targets, revisions, the manifest the CLI pulls, overrides and policies.