FDA Drug Adverse Events Scraper - FAERS Reports
Pricing
from $2.00 / 1,000 results
FDA Drug Adverse Events Scraper - FAERS Reports
Search public FDA adverse-event reports by drug and export reactions, seriousness flags, implicated products, dates, and provenance without reporter identifiers.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Thirdwatch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 hours ago
Last modified
Share
FDA Drug Adverse Events Scraper
Export structured public FDA FAERS public adverse-event reports for discovery, comparison, monitoring, and governance.
What you get
Search the public FDA FAERS catalog and save one deduplicated row per public adverse-event report. Results include report identity, dates, countries, seriousness flags, reaction terms, implicated products, indications, routes, and FDA provenance. Use discovery inputs for market maps and exact-name inputs, when available, for stable monitoring cohorts.
Output fields
| Field group | Description |
|---|---|
| Identity | Canonical safetyReportId, display name, and source URL. |
| Time evidence | Effective, filing, award, report, or catalog dates when published by the source. |
| Measures and status | Public amounts, counts, scores, or status evidence available from the source. |
| Ownership and links | Public organization, agency, product, committee, artist, or source references. |
| Classification | Public tags, categories, keywords, packaging, or status values. |
| Provenance | Search query and named upstream source for traceable analysis. |
Example output
{"safetyReportId":"12345678","receivedDate":"20260701","serious":true,"reactions":[{"term":"Rash","outcome":"6"}],"drugs":[{"name":"ASPIRIN","characterization":"1"}],"source":"FDA Adverse Event Reporting System via openFDA"}
Input parameters
| Parameter | Required | Description |
|---|---|---|
drugNames | Yes | Up to ten brand or generic medicinal-product names. |
receivedDateFrom | No | Inclusive YYYY-MM-DD lower bound. |
receivedDateTo | No | Inclusive YYYY-MM-DD upper bound. |
seriousOnly | No | Restrict output to reports encoded as serious. |
maxResultsPerQuery | Yes | Maximum reports per drug. |
maxResults | Yes | Maximum unique reports saved. |
At least one discovery or exact-name input is required. Result limits apply after cross-input deduplication, and only saved unique rows are charged.
Use cases
- Developers: discover alternatives and compare public release evidence.
- Platform teams: monitor versions, tags, compatibility, and activity for a fixed portfolio.
- Security teams: build an evidence inventory before joining vulnerability and deployment data.
- Product researchers: map a developer ecosystem with repeatable queries and dated snapshots.
Limitations
FAERS reports are unverified safety reports, not proof that a product caused an event. The Actor excludes reporter, sender, company-case, patient-demographic, and narrative fields and must not be used for medical decisions.
Compared to alternatives
Current Apify Store alternatives include maydit/us-fda-adverse-events-scraper and automation-lab/fda-maude-adverse-events-scraper. Thirdwatch combines discovery and bounded monitoring inputs where the source permits them, saves canonical evidence URLs, deduplicates before charging, provides exactly four PPE tiers, and ships ten ready-to-save Task recipes plus a five-article workflow library. Compare current Store listings directly because competitor features and pricing can change.
FAQ
Does this Actor access private packages or accounts?
No. It collects only metadata available from the public source and does not sign in, bypass access controls, or request private registry credentials.
How should I monitor a fixed portfolio?
Use exact names where supported, keep result limits explicit, save the input as an Apify Task, and retain dated datasets. Do not let an empty or failed run overwrite the previous successful snapshot.
Does a public record prove the final conclusion?
No. Public-source records are evidence for analysis, not the analysis itself. Keep provenance, apply documented rules separately, and require qualified review for high-stakes decisions.
Where can I find more workflows?
Visit Thirdwatch public-data scrapers and other Thirdwatch Actors, including GitHub, npm, and OSV Actors.
Last verified: 2026-07