Skip to main content
The catalogue endpoints describe what the server offers and who is attached to it. They are read-only and need the VIEWER role. Responses use the envelope.

List plugins

GET /api/plugins Returns every registered plugin type with its category. Use the type values as the type of a node in a workflow. Response data: an array.

Get a plugin

GET /api/plugins/{type} Returns what a plugin does, how to configure it and what it can output. Editors use configSchema to build a form for a node. Response data Each entry of configSchema describes one option: A SECRET option takes a reference such as decrypted:<key> rather than the secret itself. Errors: 404 if no plugin has that type. The error lists a field error on type.
The response below is abridged: usagePattern and the HTML of uiDesign are shortened and some descriptions are reworded.
The plugin pages describe each built-in type: Plugins overview.

List supervisors

GET /api/supervisors Lists the supervisors and control-plane plugins running on the control bus, in the order they review commands. The counts start at zero when the server starts. See Supervisors and Control planes. Response data: an array, one entry per supervisor.
An empty array means none is configured.

List workers

GET /api/workers Lists the remote workers that are connected and keep their lease, ordered by worker id. See Remote workers. Response data: an array, one entry per worker.