POST /v1/pipelines
Create a Pipeline
Create a new pipeline entity with tasks, schedules, owners, tags, and lineage information within a pipeline service using the Collate REST API for orchestration tracking.
POST
POST /v1/pipelines
Create a Pipeline
Create a new pipeline within a pipeline service.Body Parameters
string
required
Name of the pipeline. Must be unique within the parent pipeline service.
string
required
Fully qualified name of the parent PipelineService (e.g.,
sample_airflow).string
Human-readable display name for the pipeline.
string
Description of the pipeline in Markdown format.
string
URL to the pipeline definition in the source system (e.g., Airflow DAG URL).
array
Array of pipeline tasks representing individual steps in the pipeline.
array
Array of owner references (users or teams) to assign to the pipeline.
string
Fully qualified name of the domain to assign for governance purposes.
array
Array of classification tags to apply to the pipeline.
object
Custom property values defined by your organization’s metadata schema.
POST /v1/pipelines
Returns
Returns the created pipeline object with all specified properties and system-generated fields.Response
string
Unique identifier for the pipeline (UUID format).
string
Pipeline name.
string
Fully qualified name in format
service.pipelineName.string
Human-readable display name.
string
Description of the pipeline in Markdown format.
string
URL to the pipeline in the source system.
object
Reference to the parent pipeline service.
string
Type of pipeline service (e.g., Airflow, Dagster, DBTCloud).
array
List of tasks in the pipeline.
array
List of owners assigned to the pipeline.
array
Domain assignments for governance.
array
Classification tags applied to the pipeline.
object
Custom property values defined by your organization’s metadata schema.
number
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/pipelines instead of POST to perform an upsert. If a pipeline with the same fullyQualifiedName already exists, it will be updated; otherwise, a new pipeline is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead. However, for certain fields (such as description, tags, owners, and custom properties), PUT preserves an already-populated value instead of overwriting it with an empty or omitted one — the exact behavior depends on the field and the calling user or bot’s permissions, not a blanket rule. See Entity Update Behavior for the full preserve/merge rules. Use PATCH to intentionally replace an existing value.Bulk Create or Update (PUT)
UsePUT /v1/pipelines/bulk to create or update multiple pipelines in a single request. The request body is an array of create request objects.