POST /v1/services/pipelineServices
Create a Pipeline Service
Create a new pipeline service connection
POST
POST /v1/services/pipelineServices
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 Service
Create a new pipeline service connection to a platform such as Airflow, Dagster, or Fivetran.Body Parameters
Name of the pipeline service. Must be unique across all pipeline services.
Type of pipeline service (e.g.,
Airflow, GluePipeline, Airbyte, Dagster, Fivetran, DBTCloud, Nifi, DomoPipeline, CustomPipeline, Flink, KafkaConnect, SplineProducer, OpenLineage).Connection configuration specific to the service type.
Human-readable display name for the pipeline service.
Description of the pipeline service in Markdown format.
Array of owner references (users or teams) to assign to the service.
Fully qualified name of the domain to assign for governance purposes.
Array of classification tags to apply to the pipeline service.
POST /v1/services/pipelineServices
Returns
Returns the created pipeline service object with all specified properties and system-generated fields.Response
Unique identifier for the pipeline service (UUID format).
Pipeline service name.
Fully qualified name of the service.
Human-readable display name.
Description of the pipeline service in Markdown format.
Type of pipeline service (e.g., Airflow, Dagster, Fivetran).
Connection configuration for the service.
List of owners assigned to the pipeline service.
Fully qualified name of the assigned domain.
Classification tags applied to the pipeline service.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/services/pipelineServices instead of POST to perform an upsert. If a pipeline service with the same fullyQualifiedName already exists, it will be updated; otherwise, a new service 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/services/pipelineServices/bulk to create or update multiple pipeline services 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 pipeline services |
409 | ENTITY_ALREADY_EXISTS | Pipeline service with same name already exists (POST only) |