Drata Python API Docs | dltHub
Build a Drata-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Drata is a compliance automation platform that provides a Public API to push and pull compliance, control, event, evidence, and related organizational data. The REST API base URL is https://public-api.drata.com and all requests require a Bearer token for authentication.
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 Drata data in under 10 minutes.
What data can I load from Drata?
Here are some of the endpoints you can load from Drata:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| controls | public/controls | GET | data | Find controls by search terms and filters; returns paginated object with total and data array. |
| events | public/events | GET | data | Find events by filters; returns paginated object with total and data array. |
| controls_bulk | public/controls?page={page}&limit={limit} | GET | data | Bulk export/pagination examples show limit default 50 and page parameters. |
| events_bulk | public/events?page={page}&limit={limit}&sort=CREATED&sortDir=DESC | GET | data | Bulk event export example; clients iterate pages until total reached. |
| api_keys | (UI) Settings → API Keys | N/A | Manage API keys via the dashboard. |
How do I authenticate with the Drata API?
Drata uses bearer API keys. Include the API key as an HTTP Authorization header: Authorization: Bearer <API_KEY>.
1. Get your credentials
- In Drata, open Settings (bottom‑left account menu) → API Keys.
- Click Create API Key.
- Fill Name, Expiration (12 months/Never/Custom), Allowed IP Addresses (optional) and select scopes.
- Save and copy the full API key immediately — it is shown only once.
- Store the key securely and use it in requests; revoke or edit scopes from the API Keys table as needed.
2. Add them to .dlt/secrets.toml
[sources.drata_source] api_key = "your_drata_api_key_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 Drata 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 drata_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline drata_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset drata_data The duckdb destination used duckdb:/drata.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline drata_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 controls and events from the Drata 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 drata_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://public-api.drata.com", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "controls", "endpoint": {"path": "public/controls", "data_selector": "data"}}, {"name": "events", "endpoint": {"path": "public/events", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="drata_pipeline", destination="duckdb", dataset_name="drata_data", ) load_info = pipeline.run(drata_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("drata_pipeline").dataset() sessions_df = data.events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM drata_data.events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("drata_pipeline").dataset() data.events.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 Drata 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.
Troubleshooting
Authentication failures
If you receive 401/403, verify the Authorization header uses Bearer <API_KEY> and that the key is active, correctly scoped, and not expired or revoked.
Rate limits
Drata enforces a rate limit of 500 requests per minute per unique source IP. Throttle requests and use paging (limit parameter) to stay within the limit.
Pagination and bulk export
List endpoints return a paginated object with total and data array. Use page and limit query parameters (default limit=50). Iterate pages until the number of collected records equals total. Sorting parameters such as sort=CREATED and sortDir=DESC are available for events.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Drata?
Request dlt skills, commands, AGENT.md files, and AI-native context.