How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
OpenMetadata

OpenMetadata Ingestion Pipelines API

APIs related pipelines/workflows created by the system to ingest metadata.

Documentation Provider Profile APIs.io OpenAPI GitHub

OpenMetadata Ingestion Pipelines API is one of 89 APIs that OpenMetadata publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ingestion Pipelines. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 38 operations across 30 paths, and defines 44 schemas. It is described by OpenAPI 3.0.1, at version 1.13.

Requests are made against 2 base URLs: /api, http://localhost:8585/api.

38 operations 30 paths 44 schemas 6 DELETE16 GET2 PATCH9 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.13
Base URL
https://{your-host}/api/v1
Authentication
HTTP Bearer
Contact
OpenMetadata
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

OpenMetadata Ingestion Pipelines API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 38

Across 30 paths, the API surfaces 38 operations — 6 DELETE, 16 GET, 2 PATCH, 9 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Ingestion Pipelines 38

APIs related pipelines/workflows created by the system to ingest metadata.

PUT
/v1/services/ingestionPipelines/{id}/followers
Add a follower
addFollowerToIngestionPipeline 1 param body → 200404
GET
/v1/services/ingestionPipelines/{fqn}/pipelineStatus
List of pipeline status
listPipelineStatuses_1 4 params → 200
PUT
/v1/services/ingestionPipelines/{fqn}/pipelineStatus
Add pipeline status
addPipelineStatus 1 param body → 200
POST
/v1/services/ingestionPipelines/bulk/deploy
Bulk deploy a list of Ingestion Pipeline
bulkDeployIngestion body → 200
POST
/v1/services/ingestionPipelines/logs/{fqn}/{runId}/close
Close log stream for a pipeline run
closePipelineLogStream 2 params → 200404500
GET
/v1/services/ingestionPipelines
List ingestion pipelines for metadata operations
listIngestionPipelines 11 params → 200
PUT
/v1/services/ingestionPipelines
Create or update an ingestion pipeline
createOrUpdateIngestionPipeline body → 200400
POST
/v1/services/ingestionPipelines
Create an ingestion pipeline
createIngestionPipeline body → 200400
GET
/v1/services/ingestionPipelines/name/{fqn}
Get an ingestion pipeline by fully qualified name
getSpecificIngestionPipelineByFQN 4 params → 200404
DELETE
/v1/services/ingestionPipelines/name/{fqn}
Delete an ingestion pipeline by fully qualified name
deleteIngestionPipelineByFQN 2 params → 200404
PATCH
/v1/services/ingestionPipelines/name/{fqn}
Update an ingestion pipeline using name.
patchIngestionPipeline 1 param body → default
GET
/v1/services/ingestionPipelines/{id}
Get an ingestion pipeline by Id
getIngestionPipelineByID 4 params → 200404
DELETE
/v1/services/ingestionPipelines/{id}
Delete an ingestion pipeline by Id
deleteIngestionPipeline 2 params → 200404
PATCH
/v1/services/ingestionPipelines/{id}
Update an ingestion pipeline
patchIngestionPipeline_1 1 param body → default
DELETE
/v1/services/ingestionPipelines/async/{id}
Asynchronously delete an ingestion pipeline by Id
deleteIngestionPipelineAsync 2 params → 200404
DELETE
/v1/services/ingestionPipelines/{id}/followers/{userId}
Remove a follower
deleteFollower_18 2 params → 200
DELETE
/v1/services/ingestionPipelines/{id}/pipelineStatus
Delete Pipeline Status
deletePipelineStatus 1 param → 200
DELETE
/v1/services/ingestionPipelines/{id}/pipelineStatus/{runId}
Delete pipeline status by run ID
deletePipelineStatusByRunId 2 params → 204404
POST
/v1/services/ingestionPipelines/deploy/{id}
Deploy an ingestion pipeline run
deployIngestion 1 param → 200404
GET
/v1/services/ingestionPipelines/logs/{id}/last/download
Download all logs from last ingestion pipeline run as a stream
downloadLastIngestionLogs 1 param → 200404
GET
/v1/services/ingestionPipelines/ip
Check the airflow REST host IP
checkAirflowHostIp → 200
GET
/v1/services/ingestionPipelines/logs/{id}/last
Retrieve all logs from last ingestion pipeline run
getLastIngestionLogs 3 params → 200404
GET
/v1/services/ingestionPipelines/logs/{fqn}/{runId}
Get logs for a pipeline run
getPipelineLogs 4 params → 200404
POST
/v1/services/ingestionPipelines/logs/{fqn}/{runId}
Write logs for a pipeline run
writePipelineLogs 2 params body → 200404500
GET
/v1/services/ingestionPipelines/{fqn}/pipelineStatus/{id}
Get pipeline status
getPipelineStatus 2 params → 200
GET
/v1/services/ingestionPipelines/status
Check the airflow REST status
checkRestAirflowStatus → 200
GET
/v1/services/ingestionPipelines/{id}/versions/{version}
Get a version of the ingestion pipeline
getSpecificIngestionPipelineVersion 2 params → 200404
POST
/v1/services/ingestionPipelines/kill/{id}
Mark as failed and kill any not-finished workflow or task for the ingestion pipeline
killIngestionPipelineRuns 1 param → 200404
GET
/v1/services/ingestionPipelines/history
List all entity versions within a time range
listAllEntityVersionsByTimestamp_44 5 params → 200
GET
/v1/services/ingestionPipelines/logs/{fqn}
List available runs for a pipeline
listPipelineRuns 2 params → 200404
GET
/v1/services/ingestionPipelines/{id}/versions
List ingestion workflow versions
listAllIngestionPipelineVersion 1 param → 200
PUT
/v1/services/ingestionPipelines/restore
Restore a soft deleted ingestion pipeline
restore_34 body → 200
GET
/v1/services/ingestionPipelines/logs/{fqn}/stream/{runId}
Stream logs for a pipeline run
streamPipelineLogs 2 params → 200404
GET
/v1/services/ingestionPipelines/progress/{fqn}/stream/{runId}
Stream progress updates for a pipeline run
streamPipelineProgress 2 params → 200404
POST
/v1/services/ingestionPipelines/metrics/{fqn}/{runId}
Submit operation metrics batch
submitOperationMetrics 2 params body → 200404
POST
/v1/services/ingestionPipelines/toggleIngestion/{id}
Set an ingestion pipeline either as enabled or disabled
toggleIngestionPipelineEnabled 1 param → 200404
POST
/v1/services/ingestionPipelines/trigger/{id}
Trigger an ingestion pipeline run
triggerIngestionPipelineRun 1 param → 200404
PUT
/v1/services/ingestionPipelines/progress/{fqn}/{runId}
Update pipeline progress
updatePipelineProgress 2 params body → 200404

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are IngestionPipeline (44 properties), OpenMetadataConnection (34 properties), CreateIngestionPipeline (19 properties), AirflowConfig (14 properties). Each schema is shown below with its type and property counts.

TagLabelRecognizerMetadata
object
5 properties 3 required
PipelineStatusList
object
5 properties 1 required
IngestionPipelineList
object
5 properties 1 required
OperationMetric
object
9 properties 3 required
StackTraceError
object
3 properties 2 required
ChangeSummaryMap
object
AccessDetails
object
3 properties 1 required
Progress
object
RestoreEntity
object
1 property 1 required
FieldChange
object
3 properties
CoverImage
object
2 properties
FilterPattern
object
2 properties
LifeCycle
object
3 properties
OpenMetadataConnection
object
34 properties 1 required
EntityHistory
object
2 properties 2 required
AssetCertification
object
3 properties 3 required
ResultList
object
5 properties 1 required
IngestionPipeline
object
44 properties 4 required
SourceConfig
object
1 property
Paging
object
5 properties 1 required
ComponentConfig
object
JsonPatch
object
PipelineServiceClientResponse
object
4 properties 2 required
ChangeDescription
object
5 properties
AirflowConfig
object
14 properties
ElasticsSearch
object
2 properties 1 required
OperationMetricsBatch
object
4 properties 3 required
PipelineStatus
object
8 properties
ChangeEvent
object
14 properties 5 required
UsageStats
object
2 properties 1 required
Style
object
3 properties
Votes
object
4 properties
StepSummary
object
11 properties 1 required
ProgressUpdate
object
7 properties 3 required
TagLabel
object
13 properties 4 required
PatternMatch
object
3 properties 2 required
ExtraHeaders
object
TagLabelMetadata
object
2 properties
EntityError
object
2 properties
CreateIngestionPipeline
object
19 properties 5 required
OperationMetrics
object
EntityReference
object
9 properties 2 required
OpenMetadataJWTClientConfig
object
1 property 1 required
UsageDetails
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmetadata-ingestion-pipelines-api-openapi.yml Raw ↑

Other APIs OpenMetadata publishes across the network.

OpenMetadata Agent Executions API
AE Profile APIs.io
OpenMetadata AI Applications API
AE Profile APIs.io
OpenMetadata AI Governance Policies API
AE Profile APIs.io
OpenMetadata API Collections API
AE Profile APIs.io
OpenMetadata API Endpoint API
AE Profile APIs.io
OpenMetadata API Services API
AE Profile APIs.io
OpenMetadata Apps API
AE Profile APIs.io
OpenMetadata Audit Logs API
AE Profile APIs.io
OpenMetadata Bots API
AE Profile APIs.io
OpenMetadata ChangeSummary API
AE Profile APIs.io
OpenMetadata Charts API
AE Profile APIs.io
OpenMetadata Classifications API
AE Profile APIs.io
#Ingestion Pipelines
← Back to O APIs
API Details
ID
openmetadata:openmetadata-ingestion-pipelines-api
Base URL
https://{your-host}/api/v1
Docs
https://docs.open-metadata.org/latest/main-concepts/metadata-standard/apis
Provider
OpenMetadata
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=openmetadata-ingestion-pipelines-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/openmetadata-ingestion-pipelines-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of OpenMetadata Ingestion Pipelines API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.