openFDA Python API Docs | dltHub
Build a openFDA-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
openFDA provides APIs for accessing FDA public data on drugs, devices, and foods. The API returns results in JSON format. The latest updates include new datasets on adverse events and drug shortages. The REST API base URL is https://api.fda.gov and optional API key via query parameter (no required authentication for public usage).
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 openFDA data in under 10 minutes.
What data can I load from openFDA?
Here are some of the endpoints you can load from openFDA:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| drug_event | /drug/event.json | GET | results | Adverse event reports (FAERS) |
| drug_label | /drug/label.json | GET | results | Structured drug labeling (SPL) and labeling information |
| drug_enforcement | /drug/enforcement.json | GET | results | Drug recall and enforcement reports |
| drug_ndc | /drug/ndc.json | GET | results | National Drug Code directory records |
| device_event | /device/event.json | GET | results | Medical device adverse event reports |
| food_enforcement | /food/enforcement.json | GET | results | Food recall and enforcement reports |
| device_registration_listing | /device/registrationlisting.json | GET | results | Device registration and listing records |
| device_recalls | /device/enforcement.json | GET | results | Device recall and enforcement reports |
| other_endpoints_note | /[resource]/search.json or .json | GET | results | Most openFDA noun endpoints follow the same pattern and return paginated results under the top‑level "results" key; a top‑level "meta" key contains metadata. |
How do I authenticate with the openFDA API?
openFDA is public and does not require authentication for basic requests. To increase rate limits, supply an API key as the api_key query parameter.
1. Get your credentials
- Register for an API key at https://api.data.gov/signup/. 2) Confirm your email and copy the provided API key. 3) Use the key with openFDA by adding ?api_key=YOUR_KEY to requests or by configuring your client to include it as a query parameter.
2. Add them to .dlt/secrets.toml
[sources.openfda_source] api_key = "your_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 openFDA 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 openfda_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline openfda_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset openfda_data The duckdb destination used duckdb:/openfda.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline openfda_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_event and drug_label from the openFDA 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 openfda_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.fda.gov", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "drug_event", "endpoint": {"path": "drug/event.json", "data_selector": "results"}}, {"name": "drug_label", "endpoint": {"path": "drug/label.json", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="openfda_pipeline", destination="duckdb", dataset_name="openfda_data", ) load_info = pipeline.run(openfda_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("openfda_pipeline").dataset() sessions_df = data.drug_event.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM openfda_data.drug_event LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("openfda_pipeline").dataset() data.drug_event.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 openFDA 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 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 openFDA?
Request dlt skills, commands, AGENT.md files, and AI-native context.