Registry API
Telemetry
Ingest telemetry events, record workflow executions and read the analytics.
Events go through the event schema and the redaction guard before they are stored, and are kept for the organization’s retention days (90 by default). The cleanup route deletes events past retention.
Workflow executions record runs of a workflow asset by phase and status. The analytics routes back the web console’s adoption, drift, CI compliance, health and provider views.
Operations
| Request | What it does |
|---|---|
| POST /api/telemetry/events | Ingest telemetry events |
| POST /api/telemetry/cleanup | Delete events past retention |
| POST /api/telemetry/executions | Start a workflow execution record |
| GET /api/telemetry/executions | List workflow executions |
| PATCH /api/telemetry/executions/{id} | Update a workflow execution |
| GET /api/telemetry/analytics/adoption | Adoption analytics |
| GET /api/telemetry/analytics/drift | Drift analytics |
| GET /api/telemetry/analytics/ci-compliance | CI compliance analytics |
| GET /api/telemetry/analytics/health | Health analytics |
| GET /api/telemetry/analytics/providers | Provider usage analytics |
Operations are exactly those in the committed OpenAPI document (packages/workloom-api/openapi.json), which matches the route definitions; this site checks its list against both. Paths are under the API host. Public, approved packages and profiles can be read without a token; everything else needs one.