What does Drug & Device Recall Monitor — openFDA, By Firm return?

It returns 18 documented output fields: matchedFirm, category, recallNumber, status, classification, classificationSeverity, recallingFirm, brandName, genericName, productDescription, reasonForRecall and productQuantity. Each field declares its type, a description of what it holds, and an example value. The remaining 6 are listed in the output schema below.

What input does Drug & Device Recall Monitor — openFDA, By Firm require?

firms is required. A further 3 inputs are optional. The full input schema, with types and defaults, is below.

Does Drug & Device Recall Monitor — openFDA, By Firm need an API key or login?

Yes — openFdaApiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.

How do I run Drug & Device Recall Monitor — openFDA, By Firm?

It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.

Drug & Device Recall Monitor — openFDA, By Firm

Drug and device recalls matched against your firm watchlist, from FDA's free official openFDA enforcement API. FDA's own Class I/II/III severity is passed through directly — Class I is FDA's most severe designation. No API key required for normal use.

Drug & Device Recall Monitor — openFDA, By Firm returns 18 documented output fields, including matchedFirm, category, recallNumber, status and classification. Every field carries a declared type, a written description and an example value. 18 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription

18: Output fields
4: Inputs
18: Runs
2026-10-16: Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

Field	Type	What it holds	Example
matchedFirm	stringnull	Firm that matched.	<matchedFirm>
category	stringnull	Category this record belongs to, as classified upstream.	electronics
recallNumber	stringnull	Identifier of the recall.	2026-10432
status	stringnull	Outcome recorded for this row.	ok
classification	stringnull	Classification assigned by the source.	<classification>
classificationSeverity	integernull	Severity implied by the classification.	0
recallingFirm	stringnull	Firm that issued the recall.	<recallingFirm>
brandName	stringnull	Brand the product is sold under.	<brandName>
genericName	stringnull	Generic or non-proprietary name, where the source publishes one.	<genericName>
productDescription	stringnull	Product description as the merchant publishes it.	<productDescription>
reasonForRecall	stringnull	Stated reason for the recall.	<reasonForRecall>
productQuantity	stringnull	Quantity of the product.	<productQuantity>
distributionPattern	stringnull	How the matches are distributed across the results.	<distributionPattern>
voluntaryMandated	stringnull	Whether the action was voluntary or mandated.	<voluntaryMandated>
recallInitiationDate	stringnull	Date the recall process began.	<recallInitiationDate>
reportDate	stringnull	Date the report was issued.	2026-10-15
state	stringnull	State, province or region name.	active
verdict	stringnull	The Actor's conclusion for this row, stated in words.	pass

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "matchedFirm": "<matchedFirm>",
  "category": "electronics",
  "recallNumber": "2026-10432",
  "status": "ok",
  "classification": "<classification>",
  "classificationSeverity": 0,
  "recallingFirm": "<recallingFirm>",
  "brandName": "<brandName>"
}

03 — input

What you give it

Input	Type	Description
firms	arrayrequired	Manufacturer/firm names to watch, e.g. Pfizer, Medtronic. One firm per line.
categories	arrayoptional	Which recall categories to check. Both by default.
daysBack	integeroptional	How many days of recalls to check, up to 5 years.
openFdaApiKey	stringoptional	Secret — supply your own value.

04 — run

Run Drug & Device Recall Monitor on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

Also in developer tools, business

05 — questions

Asked before running it

18 of 18 fields described

What does Drug & Device Recall Monitor — openFDA, By Firm return?: It returns 18 documented output fields: matchedFirm, category, recallNumber, status, classification, classificationSeverity, recallingFirm, brandName, genericName, productDescription, reasonForRecall and productQuantity. Each field declares its type, a description of what it holds, and an example value. The remaining 6 are listed in the output schema below.
What input does Drug & Device Recall Monitor — openFDA, By Firm require?: firms is required. A further 3 inputs are optional. The full input schema, with types and defaults, is below.
Does Drug & Device Recall Monitor — openFDA, By Firm need an API key or login?: Yes — openFdaApiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.
How do I run Drug & Device Recall Monitor — openFDA, By Firm?: It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.