Registry
Get Pipeline
Retrieve details of a specific pipeline from the registry
GET
Overview
This endpoint returns the full details of a specific pipeline, including its components, configuration schema, input/output port definitions, and graph edges.Request
The unique pipeline identifier
Response
Unique pipeline identifier
Pipeline key
Pipeline version
Human-readable pipeline name
Pipeline description
Pipeline type (
batch or training)Map of component names to component IDs
Default configuration per component, each with
parallelism and config fieldsJSON Schema for the full pipeline configuration
User-facing JSON Schema for configurable parameters
Pipeline graph edges, each with
from, output, to, and input fields describing component connectionsInput port definitions, each with:
name— Display namedescription— Human-readable descriptionmode—plain_file_list(a simple list of inputs) orn_shot_file_list(labeled few-shot example files where each item carriesmetadata.class)distribute—scatter(fan inputs across workers) orreplicate(every worker receives the full list)required— Whether the port must be suppliedtracked— Whether files attached to this port participate in per-input lifecycle tracking (pending → processing → completed/failed).falsefor reference ports like n-shot examples — those inputs land in the terminalreferencestatus and never transition.
Output port definitions, each with
name and description fieldsRetry policy configuration
Visibility level:
platform (all orgs) or org (owning org only)Owning organization identifier
Registry status:
draft, published, deactivated, or deletedCreation timestamp
Last update timestamp