Skip to content
Workloom
Menu

Registry API

Packages

Create packages, publish immutable versions, manage assets, approvals, render previews and reviews.

A package is named @scope/name and owned by an organization; each package version is immutable. These operations create and update packages, add versions and assets, move a version through draft, review, published and deprecated, record version approvals and diff two versions’ asset manifests.

The render operation previews one version’s files for a provider (claude, codex, copilot or gemini). The registry runs the authoritative secret scan when a version is created.

Operations

Packages operations
RequestWhat it does
GET /packages/List packages
POST /packages/Create a package
GET /packages/{name}Get a package
PUT /packages/{name}Update a package
DELETE /packages/{name}Delete a package
POST /packages/{name}/versionsCreate a package version
GET /packages/{name}/versionsList package versions
GET /packages/{name}/versions/{version}Get a package version
DELETE /packages/{name}/versions/{version}Delete a package version
GET /packages/{name}/diffDiff two versions’ asset manifests
PATCH /packages/{name}/versions/{version}/publishPublish a version
PATCH /packages/{name}/versions/{version}/statusChange a version’s status
POST /packages/{name}/versions/{version}/approveApprove or reject a version
GET /packages/{name}/assets/{assetId}Get an asset
PUT /packages/{name}/assets/{assetId}Replace an asset
POST /packages/{name}/assetsAdd an asset
GET /packages/{name}/versions/{version}/renderRender preview for a provider
POST /packages/{name}/versions/{version}/reviewsRequest a review
GET /packages/{name}/versions/{version}/reviews/latestLatest review of a version

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.