Linking openFDA as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The openFDA connector syncs drug events, drug labels, drug ndc, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Pull U.S. FDA drug, device, and food data - adverse event reports, recalls, drug labeling, 510(k) clearances, and the NDC directory - .
An API key is optional but recommended. Without one, openFDA limits you to 1,000 requests/day per IP; with one, 120,000 requests/day. Get a free key from the openFDA API basics page.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All openFDA tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key (optional) | password | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
drug_events | Adverse event and medication error reports submitted to the FDA (FAERS). One row per safety report. | Incremental, Full refresh | receivedate | safetyreportid |
drug_labels | Structured Product Labeling (SPL) — the FDA-approved prescription and OTC drug labeling content. One row per label document. | Full refresh | — | id |
drug_ndc | National Drug Code (NDC) Directory — every drug product currently or recently marketed in the U.S. One row per product. | Full refresh | — | product_id |
drug_enforcement | Drug recall enforcement reports — recalls of drug products classified by the FDA. One row per recall. | Incremental, Full refresh | report_date | recall_number |
device_events | Medical device adverse event reports (MAUDE). One row per report of a device suspected of a death, injury, or malfunction. | Incremental, Full refresh | date_received | mdr_report_key |
device_510k | 510(k) premarket notification clearances — devices cleared by the FDA as substantially equivalent to a legally marketed device. One row per clearance. | Incremental, Full refresh | decision_date | k_number |
device_enforcement | Medical device recall enforcement reports. One row per recall. | Incremental, Full refresh | report_date | recall_number |
food_enforcement | Food recall enforcement reports. One row per recall. | Incremental, Full refresh | report_date | recall_number |
food_events | Food and cosmetic adverse event reports (CAERS). One row per report submitted to the FDA. | Incremental, Full refresh | date_created | report_number |
Troubleshooting
- If the connection fails with an authorization error, the API key (optional) is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.