Report where the served catalog comes from
Answers 'can this instance actually RUN anything right now?' in one small response, without downloading the catalog.
The catalog is published BY THE WORKERS, and the API serves the intersection across every live worker — so a piece appears only once every worker can run it. source: fleet means live workers are checked in. last-known (nothing checked in, serving the last published catalog) and compiled (nothing has ever been published) both mean degraded: true: pieces can be read and flows can be edited, but no run will execute until a worker returns.
liveCatalogs greater than 1 means a rollout is in progress and the served catalog is an intersection of two or more worker generations — a piece or version may temporarily disappear until the fleet is on one build.
fingerprint is the same value that prefixes the ETag on GET /api/pieces, so a caller can detect a catalog change cheaply by polling this endpoint.
Authorization
bearerAuth An API token: Authorization: Bearer grt_…. Mint one in the app under Settings → Workspace → API tokens; the raw value is shown once. Scopes confine the token — see x-permission on each operation.
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/api/pieces/catalog-status"{ "data": { "source": "fleet", "degraded": true, "fingerprint": "string", "pieceCount": 0, "liveCatalogs": 0 }}