Apache Atlas Python API Docs | dltHub
Build a Apache Atlas-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Apache Atlas is a metadata governance and data catalog platform that provides REST APIs for managing types, entities, lineage, and discovery. The REST API base URL is https://{atlas_host}:{port}/api/atlas/v2 and Supports HTTP Basic authentication or Kerberos/SPNEGO..
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 add "dlt[hub]" and start loading Apache Atlas data in under 10 minutes.
What data can I load from Apache Atlas?
Here are some of the endpoints you can load from Apache Atlas:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| entity_bulk | /v2/entity/bulk | GET | Bulk retrieve entities by GUIDs | |
| search_dsl | /v2/search/dsl | GET | Search entities using DSL query | |
| search_fulltext | /v2/search/fulltext | GET | Search entities using full text query | |
| search_basic | /v2/search/basic | GET | Search entities using basic terms | |
| lineage | /v2/lineage/{guid} | GET | Retrieve lineage information for an entity |
How do I authenticate with the Apache Atlas API?
Apache Atlas primarily supports HTTP Basic authentication using a username and password. Kerberos/SPNEGO authentication is also supported for secure environments, which typically requires a keytab and principal.
1. Get your credentials
Apache Atlas does not use a typical API key/dashboard setup for REST API authentication. Instead, it relies on standard enterprise authentication methods configured at the server level, primarily Kerberos, LDAP, or simple file-based authentication. To obtain credentials, you must: 1. Contact your cluster administrator to get a valid username and password (for basic or LDAP authentication) or a valid Kerberos principal and keytab file. 2. If using basic authentication, ensure your user account has the necessary permissions (often Atlas administrator privileges) assigned. 3. If the environment is Kerberos-secured, perform a 'kinit' to obtain a TGT (Ticket Granting Ticket) before making API calls.
2. Add them to .dlt/secrets.toml
[sources.apache_atlas_source] atlas_username = "your_username" atlas_password = "your_password" atlas_host = "your_atlas_host" atlas_port = 21000
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Apache Atlas 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:
uv run python apache_atlas_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline apache_atlas_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset apache_atlas_data The duckdb destination used duckdb:/apache_atlas.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 /v2/entity and /v2/types/typedefs from the Apache Atlas 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 apache_atlas_source(username=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{atlas_host}:{port}/api/atlas/v2", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": username}, }, "resources": [ {"name": "search_dsl", "endpoint": {"path": "v2/search/dsl", "data_selector": "entities"}}, {"name": "search_fulltext", "endpoint": {"path": "v2/search/fulltext", "data_selector": "entities"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="apache_atlas_pipeline", destination="duckdb", dataset_name="apache_atlas_data", ) load_info = pipeline.run(apache_atlas_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("apache_atlas_pipeline").dataset() sessions_df = data.search_dsl.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM apache_atlas_data.search_dsl LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("apache_atlas_pipeline").dataset() data.search_dsl.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 Apache Atlas data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Apache Atlas?
Request dlt skills, commands, AGENT.md files, and AI-native context.