Registry API
Administration
Teams and members, org policies and the audit log.
Teams are named groups of members, each a member or a lead. Org policies are named rules on the organization. The audit log records changes across the organization.
Operations
| Request | What it does |
|---|---|
| GET /admin/teams | List teams |
| POST /admin/teams | Create a team |
| GET /admin/teams/{teamId}/members | List team members |
| POST /admin/teams/{teamId}/members | Add a team member |
| PATCH /admin/teams/{teamId}/members/{memberId} | Change a member’s team role |
| DELETE /admin/teams/{teamId}/members/{memberId} | Remove a team member |
| GET /admin/audit | Audit log |
| GET /admin/policies | List org policies |
| POST /admin/policies | Create an org policy |
| PATCH /admin/policies/{policyId} | Update an org policy |
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.