FDA MAUDE, 510(k) & Warning Letters Scraper and Alerts avatar

FDA MAUDE, 510(k) & Warning Letters Scraper and Alerts

Pricing

$3.00 / 1,000 results

Go to Apify Store
FDA MAUDE, 510(k) & Warning Letters Scraper and Alerts

FDA MAUDE, 510(k) & Warning Letters Scraper and Alerts

Track FDA 510(k) device clearances, MAUDE adverse event reports (deaths, injuries, malfunctions) and warning letters from fda.gov in one Actor. Filter by device, company, product code or FDA office. 'Only new' mode for daily regulatory alerts. No API key, no login.

Pricing

$3.00 / 1,000 results

Rating

0.0

(0)

Developer

GovData Feeds

GovData Feeds

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 days ago

Last modified

Features

Limited permissions

Share

Track FDA medical device clearances (510(k)), MAUDE adverse event reports and FDA warning letters as clean rows, with new-record alerts.

Rate your experience: if you have used this Actor, you can tell us how it went on the reviews page. Honest feedback of any kind helps us improve it.

What it does and who it is for

One Actor, three FDA datasets, selected with the Dataset input: 510(k) (new device clearance decisions, from openFDA), MAUDE (medical device adverse event, malfunction and death reports, from openFDA) and Warning letters (the FDA warning letter listing on fda.gov). Each record has a common core (dataset, recordId, date, company, title, category, productCode, url) plus fields specific to the dataset.

Filter by keyword, company, FDA product code and date window, plus dataset-specific filters: decision and clearance type and applicant state for 510(k), event type for MAUDE, and issuing office for warning letters. Turn on Only new for alerts.

Use cases

  • Medical device makers and regulatory teams: watch competitor clearances and adverse event reports in your product code.
  • Investors and analysts: follow clearances and warning letters for listed device and drug companies.
  • Quality, safety and compliance teams: track warning letters and MAUDE reports for suppliers.
  • Consultants, law firms and journalists: a daily or weekly feed of FDA enforcement and clearance activity.
  • AI agents: answer "which companies got a new 510(k) clearance for insulin pumps this month?".

Why use this instead of the free official site or API

The underlying data is public and the official sources are free. What this Actor adds is convenience: three different FDA sources become one consistent, alert-ready feed.

What you needOfficial site / APIThis Actor
Covering clearances, adverse events and warning lettersSeparate openFDA endpoints plus a warning-letter listing page with no API of its ownOne Actor and one input; choose the dataset
Query syntaxopenFDA search syntax and paging limitsPlain input fields: keyword, company, product code, dates
Days to decisionSubtract received and decision dates yourselfdaysToDecision calculated on every 510(k) record
Only new recordsYou track IDs yourselfOnly new mode with a named alert

If you only need a single lookup now and then, the official site is fine. If you want the same data on a schedule, as flat rows you can feed to a spreadsheet, CRM or agent, this saves the glue work.

Data fields

The table shows the 510(k) record from the example below, followed by fields that only appear for MAUDE and Warning letters records. Every record also has dataset telling you which one it is.

FieldTypeWhat it contains
datasettext510k, maude or warning_letters.
recordIdtext510(k): K number. MAUDE: MDR report key. Warning letters: the letter's slug on fda.gov.
datedate510(k): decision date. MAUDE: date received. Warning letters: posted date.
companytext510(k): applicant. MAUDE: manufacturer. Warning letters: company name.
titletext510(k): device name. MAUDE: brand or generic name. Warning letters: letter subject.
categorytext510(k): decision description. MAUDE: event type. Warning letters: issuing office.
decisionCodetext510(k) only: decision code (for example SESE for Substantially Equivalent).
clearanceTypetext510(k) only: Traditional, Special, Abbreviated, Direct or Dual Track.
dateReceiveddate510(k) only: date FDA received the submission.
daysToDecisioninteger510(k) only: days between receipt and decision.
productCodetextThree-letter FDA product code.
deviceClasstextFDA device class (510(k) and MAUDE).
regulationNumbertext510(k) only: regulation number.
medicalSpecialtytext510(k) only: medical specialty or advisory committee.
statementOrSummarytext510(k) only: whether a Statement or a Summary was filed.
thirdPartyReviewboolean510(k) only: whether a third party reviewed it.
expeditedReviewtext510(k) only: expedited review flag, when given.
contacttext510(k) only: applicant contact name.
addresstext510(k) only: applicant street address.
citytext510(k) only: applicant city.
statetext510(k) only: applicant state.
ziptext510(k) only: applicant ZIP or postal code.
countrytext510(k) only: applicant country code.
urltextLink to the record on FDA's site.
sourcetextSource of the data.
scrapedAtdatetimeWhen the Actor collected the record (UTC).
reportNumbertextMAUDE only: manufacturer report number.
dateOfEventdateMAUDE only: date the event occurred.
genericNametextMAUDE only: generic device name.
modeltextMAUDE only: model number.
catalogNumbertextMAUDE only: catalog number.
lotNumbertextMAUDE only: lot number.
deviceManufacturertextMAUDE only: device manufacturer name.
reportTypetextMAUDE only: report type.
reportSourcetextMAUDE only: report source.
productProblemstextMAUDE only: product problems.
patientOutcomestextMAUDE only: patient outcomes.
patientProblemstextMAUDE only: patient problems.
devicesInEventintegerMAUDE only: number of devices in the event.
patientsInEventintegerMAUDE only: number of patients in the event.
narrativetextMAUDE only: the first up to 1,500 characters of the event description (when Include narrative is on).
letterIssueDatedateWarning letters only: date the letter was issued.
issuingOfficetextWarning letters only: FDA office that issued it.
subjecttextWarning letters only: letter subject.
marcsCmsNumbertextWarning letters only: MARCS-CMS number from the letter URL, when present.
responseLetterbooleanWarning letters only: whether a response letter is listed.
closeoutLetterbooleanWarning letters only: whether a close-out letter is listed.

Fields a source does not publish are null.

"New since yesterday" alerts

Turn on Only new and the Actor remembers what it has already returned, so each scheduled run delivers only records you have not seen before.

  1. Open the Actor in Apify Console and set the input, with Only new since last run switched on and a fixed alert name (stateKey). Example input:
{
"dataset": "maude",
"keyword": "insulin pump",
"eventTypes": ["Death", "Injury"],
"postedWithinDays": 45,
"includeNarrative": true,
"maxResults": 200,
"onlyNew": true,
"stateKey": "insulin-pump-adverse-events"
}
  1. Click Save as task, then open Schedules, create a schedule (for example the cron expression 0 7 * * * for every day at 7:00 in the time zone you pick) and add the task to it.
  2. Under the task's Integrations, send the results to Slack, email, Google Sheets, a webhook or your own system.

MAUDE is published about monthly, so use a window of 45 days or more for MAUDE. For 510(k) clearances 30 days is plenty, because openFDA publishes them weekly.

The first run returns everything that matches your window (all matching records in the window); later runs return only unseen records. Use a different alert name for each task so each keeps its own memory. A run with nothing new returns no results.

Cost per run

This Actor uses pay-per-result pricing: $3.00 per 1,000 results ($0.003 per result), with the Apify platform fee included. You are charged for the records a run returns and nothing is added on top for platform usage. A run that finds nothing new returns no results, so it has no per-result charge. The Max results input caps what a run can return (and so what it can cost).

Worked example: a weekly 510(k) alert returning 40 new clearances costs 40 × $0.003 = $0.12 per run. A pull of 2,000 MAUDE reports costs 2 × $3.00 = $6.00.

The pricing is configured in Apify Console; the Pricing tab on this page is the authoritative source if it ever differs from this text.

Example input and output

The output below comes from real test runs of this Actor. This example shows a 510(k) record; MAUDE and warning letter records have the extra fields listed above. Email addresses are masked and very long text is shortened here; the Actor returns the full values.

Input used for the example:

{
"dataset": "510k",
"keyword": "catheter",
"postedWithinDays": 60,
"clearanceTypes": ["Traditional"],
"onlyNew": true,
"stateKey": "new-catheter-clearances",
"maxResults": 3
}

Output (the first 2 records of a test run):

[
{
"dataset": "510k",
"recordId": "K262068",
"date": "2026-10-09",
"company": "CathRx, Ltd.",
"title": "Khelix Magnetic Sensor Electrophysiology Catheter (SS1-*-*-MAG)",
"category": "Substantially Equivalent",
"decisionCode": "SESE",
"clearanceType": "Traditional",
"dateReceived": "2026-06-22",
"daysToDecision": 109,
"productCode": "DRF",
"deviceClass": "2",
"regulationNumber": "870.1220",
"medicalSpecialty": "Cardiovascular",
"statementOrSummary": "Summary",
"thirdPartyReview": false,
"expeditedReview": null,
"contact": "Henry Le",
"address": "Unit 8, 2-8 S. St.",
"city": "Rydalmere",
"state": null,
"zip": "2116",
"country": "AU",
"url": "https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm?ID=K262068",
"source": "openFDA device/510k",
"scrapedAt": "2026-10-23T12:43:25.105Z"
},
{
"dataset": "510k",
"recordId": "K261649",
"date": "2026-10-09",
"company": "Stryker Neurovascular",
"title": "Excelsior Reach Microcatheter",
"category": "Substantially Equivalent",
"decisionCode": "SESE",
"clearanceType": "Traditional",
"dateReceived": "2026-05-19",
"daysToDecision": 143,
"productCode": "QJP",
"deviceClass": "2",
"regulationNumber": "870.1250",
"medicalSpecialty": "Cardiovascular",
"statementOrSummary": "Summary",
"thirdPartyReview": false,
"expeditedReview": null,
"contact": "Katelynn Kirby",
"address": "47900 Bayside Pkwy.",
"city": "Fremont",
"state": "CA",
"zip": "94538",
"country": "US",
"url": "https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm?ID=K261649",
"source": "openFDA device/510k",
"scrapedAt": "2026-10-23T12:43:25.111Z"
}
]

Limits worth knowing

  • MAUDE data is about 3 to 4 weeks behind. Use a look-back of at least 45 days for MAUDE.
  • openFDA publishes 510(k) data weekly.
  • The warning letter listing has listing fields only: there is no letter text. The Actor depends on the layout of the fda.gov warning letters page, so a page redesign could break that dataset.
  • MAUDE event narratives are cut at 1,500 characters.
  • openFDA returns an error when nothing matches; the Actor handles that and returns no results.
  • For recalls, use the separate FDA recall Actor below; this one does not return recalls.
  • With a small Max results and Only new on, each run returns the next unseen batch.

FAQ

What is a 510(k)?

A premarket notification that device makers submit to FDA to show a device is substantially equivalent to one already on the market. The dataset lists FDA's decisions.

What is MAUDE?

The FDA database of medical device adverse event, malfunction and death reports. Reports are submitted by manufacturers, clinicians and consumers; an entry does not prove the device caused the event.

Do I need an API key?

No.

Does it include the text of warning letters?

No. It returns the listing fields and the link to the letter on fda.gov.

Is this the same as FDA recalls?

No. See the FDA recall Actor below.

More Actors from GovData Feeds, all on Apify:

Data comes from openFDA and fda.gov, a US government source. This Actor is not affiliated with or endorsed by the FDA. MAUDE reports are unverified and do not establish that a device caused an event. Always confirm on the official FDA record.