openFDA Device Adverse Events Scraper

openFDA Device Adverse Events Scraper pulls structured data from openFDA (FDA Manufacturer and User Facility Device Experience) and returns it as a clean dataset you can export as JSON, CSV or Excel. It searches FDA medical device adverse event reports for a device brand name, generic name or manufacturer and returns one row per report with the event type, dates, device identifiers and reported problems.

No API key, no login. Click Start and it works with the prefilled input.

What does openFDA Device Adverse Events Scraper do?

It queries openFDA (FDA Manufacturer and User Facility Device Experience) and returns one row per record, with only the fields that matter. Runs on the Apify platform, so you get an API endpoint, scheduling, monitoring and integrations (Zapier, Make, Google Sheets, webhooks) without maintaining any infrastructure.

Why use it?

• openFDA (FDA Manufacturer and User Facility Device Experience) data without the plumbing: no proxy setup, no pagination code, no scraping maintenance.
• Schedule it to monitor changes daily or weekly and trigger alerts on new records.
• Feed it straight into a spreadsheet, database, or an AI agent via the Apify API or MCP server.
• Runs in seconds and returns a typed dataset that is ready for analysis.

How to use it

1. Click Try for free / Start.
2. Leave the default input to see a sample run, or type your own values (see Input below).
3. Press Start and wait a few seconds.
4. Open the Output tab and download as JSON, CSV, Excel or HTML.

Input

Field	Type	Default	Description
searchQuery	string	"device.brand_name:pacemaker"	openFDA search expression, e.g. device.brand_name:pacemaker. Combine fields with AND or OR.
maxResults	integer	25	Maximum number of adverse event reports to return (openFDA caps each request at 100).

Example input:

{
  "searchQuery": "device.brand_name:pacemaker",
  "maxResults": 5
}

Output

One item per record. Sample:

{
  "report_key": "10000097",
  "report_number": "3004593495-2020-00473",
  "event_type": "Malfunction",
  "date_received": "20200427",
  "date_of_event": "20200402",
  "brand_name": "SURESCAN"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data fields

Field	Type	Meaning
report_key	string	Report Key
report_number	string	Report Number
event_type	string	Event Type
date_received	string	Received
date_of_event	string	Event Date
brand_name	string	Device Brand
generic_name	string	Device Type
device_manufacturer	string	Device Manufacturer
product_code	string	Product Code
manufacturer_name	string	Reported Manufacturer
problems	string	Reported Problems
devices_in_event	integer	Devices In Event
patients_in_event	integer	Patients In Event
adverse_event_flag	string	Adverse Event
remedial_action	string	Remedial Action

How much does it cost to run?

This Actor uses pay-per-event pricing: you pay per result item pushed to the dataset, and nothing for an empty run. Each run is a few seconds of compute, so typical costs are fractions of a cent per run, and the Apify free tier covers plenty of testing.

Tips and advanced options

• Raise maxResults for a bigger pull; the Actor pages through the source for you.
• Schedule it (e.g. every morning) and combine with a webhook to get only the new records.
• Add the Actor to an AI agent through the Apify MCP server for natural-language queries.

FAQ, disclaimers and support

• Is this legal? It uses publicly available data from openFDA (FDA Manufacturer and User Facility Device Experience). You are responsible for how you use the data and for complying with the source's terms.
• It returned nothing? Use an openFDA search field such as device.brand_name:pacemaker, device.generic_name:catheter or manufacturer_name:"Medtronic".
• Something broken? Open an issue on the Actor's Issues tab. Data sources change and get fixed quickly.
• Need a custom variant (extra fields, a different source, a scheduled report)? Get in touch through the Issues tab.