# FDA Adverse Event Reports (openFDA) (`texxupport/fda-adverse-events`) Actor

- **URL**: https://apify.com/texxupport/fda-adverse-events.md
- **Developed by:** [Kye Williams](https://apify.com/texxupport) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 adverse event reports

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## FDA Adverse Event Reports (openFDA)

Search and monitor FDA adverse event reports for **drugs and biologics (FAERS)** or **medical devices (MAUDE)** through the official openFDA API. Filter by product, manufacturer, reaction, seriousness and date, and schedule it to receive **only reports you have not seen yet**.

**Who uses it:** pharmacovigilance and drug-safety teams, medical device quality and regulatory staff, product liability and mass-tort law firms, healthcare investors and analysts, journalists and researchers.

### What you get

**Drug reports:** report id, received date, serious / death / hospitalization / life-threatening flags, suspect drugs and other drugs taken, generic names, manufacturers, reactions (MedDRA terms) and their outcomes, patient sex and age, reporter country, report type.

**Device reports:** report number, received and event dates, event type (death, injury, malfunction), device brand and generic names, manufacturer, model numbers, product codes, product problems and the report narrative.

### How to use it

1. Choose drugs or devices.
2. Enter at least one product, manufacturer or (for drugs) reaction.
3. Optional: only serious reports, or only those involving a death.
4. Schedule it weekly with **Only reports not delivered before** on.

An optional free openFDA API key (from open.fda.gov) raises the daily limit; it is stored as a secret.

### Cost

Priced per report delivered.

### Important

- Adverse event reports are unverified and can be duplicates. A report does **not** prove a product caused the event. This is not medical advice.
- Data: openFDA (api.fda.gov), US government work. Not affiliated with or endorsed by the FDA.
- openFDA lets one search page through at most about 25,000 reports; narrow the dates for larger result sets.

# Actor input Schema

## `kind` (type: `string`):

Which reports to search: drug reports (FAERS) or medical device reports (MAUDE).

## `products` (type: `array`):

Brand or generic names, for example Ozempic or semaglutide, or a device brand. A report matches if it names any of them.

## `manufacturers` (type: `array`):

Company names as the FDA records them, for example Novo Nordisk A/S.

## `reactions` (type: `array`):

MedDRA reaction terms, for example Pancreatitis or Nausea.

## `seriousOnly` (type: `boolean`):

Drugs: marked serious. Devices: death or injury.

## `deathsOnly` (type: `boolean`):

Only include reports that involve a death.

## `daysBack` (type: `integer`):

Used when no From date is set. The FDA publishes reports in batches, so the newest few weeks are often empty; 90 days reliably reaches published data.

## `dateFrom` (type: `string`):

Only include reports received on or after this date (format YYYY-MM-DD). Leave empty to use the days-back setting.

## `dateTo` (type: `string`):

Only include reports received on or before this date (format YYYY-MM-DD). Leave empty for no end date.

## `onlyNew` (type: `boolean`):

Turn on for scheduled runs. Skip reports that were already delivered in a previous run, so each report is delivered once.

## `apiKey` (type: `string`):

Free from open.fda.gov. Without one, openFDA allows about 1,000 requests a day from shared addresses, which can run out. With one, 120,000 a day.

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

Stop after this many reports have been delivered in one run.

## Actor input object example

```json
{
  "kind": "drug",
  "products": [
    "Ozempic"
  ],
  "seriousOnly": false,
  "deathsOnly": false,
  "daysBack": 90,
  "onlyNew": false,
  "maxResults": 200
}
```

# Actor output Schema

## `results` (type: `string`):

Every row delivered by this run, as a table you can download as CSV, Excel or JSON.

# 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 = {
    "products": [
        "Ozempic"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("texxupport/fda-adverse-events").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 = { "products": ["Ozempic"] }

# Run the Actor and wait for it to finish
run = client.actor("texxupport/fda-adverse-events").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 '{
  "products": [
    "Ozempic"
  ]
}' |
apify call texxupport/fda-adverse-events --silent --output-dataset

```

## MCP server setup

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

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/wUjjHTEf14MkLQVWg/builds/4R2FXdxqwx6bjdeLQ/openapi.json