POST /v1/pipelines
Create a Pipeline
Create a new pipeline within a pipeline service
POST
POST /v1/pipelines
Documentation Index
Fetch the complete documentation index at: https://openmetadata-codex-audit-docs-codebase-alignment.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Create a Pipeline
Create a new pipeline within a pipeline service.Body Parameters
Name of the pipeline. Must be unique within the parent pipeline service.
Fully qualified name of the parent PipelineService (e.g.,
sample_airflow).Human-readable display name for the pipeline.
Description of the pipeline in Markdown format.
URL to the pipeline definition in the source system (e.g., Airflow DAG URL).
Array of pipeline tasks representing individual steps in the pipeline.
Array of owner references (users or teams) to assign to the pipeline.
Fully qualified name of the domain to assign for governance purposes.
Array of classification tags to apply to the pipeline.
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
Unique identifier for the pipeline (UUID format).
Pipeline name.
Fully qualified name in format
service.pipelineName.Human-readable display name.
Description of the pipeline in Markdown format.
URL to the pipeline in the source system.
Reference to the parent pipeline service.
Type of pipeline service (e.g., Airflow, Dagster, DBTCloud).
List of tasks in the pipeline.
List of owners assigned to the pipeline.
Domain assignments for governance.
Classification tags applied to the pipeline.
Custom property values defined by your organization’s metadata schema.
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.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.
Error Handling
| Code | Error Type | Description |
|---|---|---|
400 | BAD_REQUEST | Invalid request body or missing required fields |
401 | UNAUTHORIZED | Invalid or missing authentication token |
403 | FORBIDDEN | User lacks permission to create pipelines |
409 | ENTITY_ALREADY_EXISTS | Pipeline with same name already exists in service (POST only) |