# FDA Recalls Monitor - Drug, Device & Food to JSON (`aaddss/fda-recalls-monitor`) Actor

Search & monitor FDA recalls (drug, device, food) via the official openFDA API. Filter by keyword, status, classification. Clean structured JSON for compliance, legal, pharma and research.

- **URL**: https://apify.com/aaddss/fda-recalls-monitor.md
- **Developed by:** [lxraa](https://apify.com/aaddss) (community)
- **Categories:** Business, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 recall records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FDA Recalls Monitor — Drug, Device & Food Recalls → JSON (with stock tickers)

Search and monitor **FDA enforcement recalls** (drug, device, food) through the official
**openFDA** API. No browser, no proxy: a public government API, so it's fast, reliable,
and fully legal. Recall data is de-identified public enforcement information.

#### What it does

Query openFDA's enforcement datasets by category, keyword, status, and severity class,
and get clean, flattened recall records — recall reason, recalling firm, classification,
distribution, dates, and more.

#### Bonus: recalling firm → stock ticker

A recall is a market-moving event. When the recalling firm is a publicly-traded company,
this actor maps it to its **stock ticker + SEC CIK** (via SEC's official company list,
with a conservative match plus an alias table for big pharma like JNJ/PFE/ABBV). Most
recallers are private or foreign generic makers (so `ticker` is often `null`) — but when
it matches, you get a high-signal, ticker-tagged event. Turn it off with `mapTickers: false`.

#### Input

| Field | Description |
|-------|-------------|
| `category` | `drug`, `device`, or `food` |
| `keyword` | Optional term matched on product description (e.g. `insulin`) |
| `status` | `Ongoing`, `Completed`, `Terminated`, `Pending`, or empty for all |
| `classification` | `Class I` (most serious), `Class II`, `Class III`, or empty |
| `maxResults` | Max recalls to return |
| `mapTickers` | Add ticker + CIK for matched recalling firms (default `true`) |

#### Output (one item per recall)

```json
{
  "recallNumber": "D-1234-2026",
  "status": "Ongoing",
  "classification": "Class II",
  "recallingFirm": "Example Pharma Inc",
  "ticker": null,
  "cik": null,
  "reason": "Failed dissolution specifications",
  "productDescription": "...",
  "city": "Trenton", "state": "NJ", "country": "United States",
  "recallInitiationDate": "20260512",
  "reportDate": "20260601"
}
```

#### Use cases

- **Pharma / medtech / food safety** — monitor recalls in your category or by competitor.
- **Quant / alternative data** — ticker-tagged recall events as risk signals.
- **Compliance & QA** — track Class I/II recalls relevant to your supply chain.

#### Pricing

Pay-per-result (PPE): billed per recall returned. Schedule it for a fresh recall feed.

#### Legal & data notes

All data comes from the official openFDA enforcement API (public, de-identified
enforcement records). Ticker mapping uses SEC's public `company_tickers.json`.

# Actor input Schema

## `category` (type: `string`):

Which FDA enforcement dataset to query.

## `keyword` (type: `string`):

Optional term matched against the product description (e.g. "insulin", "hand sanitizer").

## `status` (type: `string`):

Recall status filter.

## `classification` (type: `string`):

Recall severity class (I = most serious).

## `maxResults` (type: `integer`):

Maximum recalls to return.

## `mapTickers` (type: `boolean`):

Add public-company ticker + SEC CIK for each recalling firm when confidently matched (via SEC's official company list). A recall is a market-moving event — this turns raw recalls into a signal-ready feed.

## Actor input object example

```json
{
  "category": "drug",
  "status": "Ongoing",
  "classification": "",
  "maxResults": 200,
  "mapTickers": true
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("aaddss/fda-recalls-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("aaddss/fda-recalls-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call aaddss/fda-recalls-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aaddss/fda-recalls-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tTcyM1szgfnJCyLu3/builds/FfkqCQz9r05DlAiQT/openapi.json