OpenMetadata Python API Docs | dltHub

Build a OpenMetadata-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

OpenMetadata REST API allows creating tables via metadata standard schemas. The endpoint is at /api/data/createtable. Refer to OpenMetadata documentation for detailed usage. The REST API base URL is https://{openmetadata_host}/api/v1 and all requests typically require a Bearer token in the Authorization header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading OpenMetadata data in under 10 minutes.


What data can I load from OpenMetadata?

Here are some of the endpoints you can load from OpenMetadata:

ResourceEndpointMethodData selectorDescription
tablesapi/v1/tablesGETdataList tables and table resources; also support GET by id/name
databasesapi/v1/databasesGETdataList databases
servicesapi/v1/servicesGETdataList registered services (databaseService, dashboardService, messagingService)
usersapi/v1/usersGETdataList users
searchapi/v1/search/queryGETdataSearch entities by query text

How do I authenticate with the OpenMetadata API?

The OpenMetadata REST API expects an Authorization header with a bearer token (Authorization: Bearer ) for authenticated requests. Include the token in every request header.

1. Get your credentials

  1. Log in to your OpenMetadata instance (web UI) as an administrator or user. 2) Navigate to Settings → Security (or your user profile) and select "Personal Access Tokens". 3) Click "Generate New Token", give it a name and optional expiration, then create it. 4) Copy the generated token and store it securely; use it as the Bearer token in API requests.

2. Add them to .dlt/secrets.toml

[sources.openmetadata_source] access_token = "your_openmetadata_bearer_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the OpenMetadata API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python openmetadata_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline openmetadata_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset openmetadata_data The duckdb destination used duckdb:/openmetadata.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline openmetadata_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads tables and databases from the OpenMetadata API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def openmetadata_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{openmetadata_host}/api/v1", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "tables", "endpoint": {"path": "api/v1/tables", "data_selector": "data"}}, {"name": "databases", "endpoint": {"path": "api/v1/databases", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="openmetadata_pipeline", destination="duckdb", dataset_name="openmetadata_data", ) load_info = pipeline.run(openmetadata_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("openmetadata_pipeline").dataset() sessions_df = data.tables.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM openmetadata_data.tables LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("openmetadata_pipeline").dataset() data.tables.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load OpenMetadata data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for OpenMetadata?

Request dlt skills, commands, AGENT.md files, and AI-native context.