FDA Python API Docs | dltHub
Build a FDA-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
openFDA is an Elasticsearch-backed public API that serves FDA data (drugs, devices, foods, recalls, adverse events, etc.). The REST API base URL is https://api.fda.gov (openFDA); https://api-datadashboard.fda.gov/v1 (FDA Data Dashboard); https://www.accessdata.fda.gov/rest/pcbapi/v1 (PCB API base path under accessdata); https://www.accessdata.fda.gov/rest/iresapi/v1 (iRES Enforcement API base path under accessdata — documented at ires/apidocs). and openFDA: optional API key passed as api_key parameter (increases rate limits); accessdata (iRES/PCB/Data Dashboard): header-based Authorization-User and Authorization-Key (OII Unified Logon) required..
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 FDA data in under 10 minutes.
What data can I load from FDA?
Here are some of the endpoints you can load from FDA:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| drug_label | /drug/label.json | GET | results | openFDA drug labeling records |
| drug_event | /drug/event.json | GET | results | openFDA adverse event reports |
| device_enforcement | /device/enforcement.json | GET | results | openFDA device enforcement/recalls |
| food_enforcement | /food/enforcement.json | GET | results | openFDA food recall enforcement records |
| device_recalls (iRES) | /rest/iresapi/v1/enforcement_reports (varies) | GET/POST | result (Data Dashboard/iRES use "result" array) | iRES Enforcement Reports API (requires Authorization headers) |
| pcb_product | /rest/pcbapi/v1/product | GET | (response is top-level list or Response Body field; PCB endpoints return JSON objects — individual endpoints documented; use product endpoints like /rest/pcbapi/v1/product/{productid}) | Product Code Builder endpoints (Authorization-User/Key required) |
| data_dashboard_dataset | /v1/{dataset} | POST (Data Dashboard uses POST) | result | Data Dashboard datasets return JSON with keys statuscode,message,resultcount,result (array) |
How do I authenticate with the FDA API?
openFDA accepts an api_key query parameter (or Basic auth username form) to raise rate limits; Data Dashboard / iRES / PCB require FDA OII Unified Logon credentials and two headers: Authorization-User (email) and Authorization-Key (FDA-generated key).
1. Get your credentials
- openFDA: request a free API key at https://open.fda.gov/apis/authentication/ (follow "Get your API key" workflow).
- iRES/PCB/Data Dashboard: request credentials via OII Unified Logon (https://www.accessdata.fda.gov/scripts/oul) and follow the application instructions; FDA will send Authorization-Key and Authorization-User (email).
2. Add them to .dlt/secrets.toml
[sources.fda_data_source] api_key = "your_openfda_api_key" authorization_user = "your_email@example.com" authorization_key = "your_fda_auth_key"
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 FDA 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 fda_data_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fda_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fda_data_data The duckdb destination used duckdb:/fda_data.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline fda_data_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 drug_label and drug_event from the FDA 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 fda_data_source(api_key (for openFDA) / authorization_user, authorization_key (for accessdata sources)=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.fda.gov (openFDA); https://api-datadashboard.fda.gov/v1 (FDA Data Dashboard); https://www.accessdata.fda.gov/rest/pcbapi/v1 (PCB API base path under accessdata); https://www.accessdata.fda.gov/rest/iresapi/v1 (iRES Enforcement API base path under accessdata — documented at ires/apidocs).", "auth": { "type": "api_key (openFDA) ; http_basic-like header pair (accessdata) — represent as "api_key" for openFDA and "custom_headers" for accessdata in dlt.", "api_key (for openFDA) ; authorization_key (for accessdata)": api_key (for openFDA) / authorization_user, authorization_key (for accessdata sources), }, }, "resources": [ {"name": "drug_label", "endpoint": {"path": "drug/label.json", "data_selector": "results"}}, {"name": "drug_event", "endpoint": {"path": "drug/event.json", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fda_data_pipeline", destination="duckdb", dataset_name="fda_data_data", ) load_info = pipeline.run(fda_data_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("fda_data_pipeline").dataset() sessions_df = data.drug_label.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fda_data_data.drug_label LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fda_data_pipeline").dataset() data.drug_label.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 FDA 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
openFDA: If requests exceed anonymous daily limits, obtain an api_key and pass as api_key parameter or Basic auth username. accessdata APIs: 401/Not Authorized occur when Authorization-User or Authorization-Key headers are missing or cached with wrong signature; use unique signatures and ensure TLS1.2.
Rate limits and quotas
openFDA: anonymous limits 240 req/min per IP and 1,000/day; with api_key 240 req/min per key and 120,000/day. Contact openFDA for higher limits.
Pagination and result selectors
openFDA: responses are JSON objects with top-level keys meta and results; the records array is in "results". Data Dashboard/iRES: responses include keys statuscode,message,resultcount,result; the records array is "result". Data Dashboard supports start/rows paging (max rows 5000) and returntotalcount to get totalrecordcount.
common_api_errors:
- openFDA returns HTTP 400 for malformed queries; Data Dashboard returns statuscode values (e.g., 401 Not Authorized, 412 No results found, 415 rows >5000, etc.) as documented.
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 FDA?
Request dlt skills, commands, AGENT.md files, and AI-native context.