# openFDA Device Adverse Events — MAUDE Reports (`alaudinburki/openfda-device-events`) Actor

Query the FDA's MAUDE database and get flat rows - report number, event type, dates, device brand and generic name, manufacturer and class.

- **URL**: https://apify.com/alaudinburki/openfda-device-events.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

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

## openFDA Device Adverse Events (MAUDE) — Medical Device Reports

Query the FDA's MAUDE database and get flat rows — report number, event type, dates, **device brand
and generic name**, manufacturer, device class and location.

### What you get

`reportNumber`, `eventType`, `dateReceived`, `dateOfEvent`, `deviceBrandName`, `deviceGenericName`,
`deviceClass`, `manufacturer`, `manufacturerCity`, `manufacturerState`.

### Sample output

```json
{ "reportNumber": "MDR-2026-1", "eventType": "Injury",
  "deviceBrandName": "ACME PUMP", "deviceClass": "2" }
```

### Limitations

- **Reporting is voluntary and lagging.** A report is not a proven causation, and the absence of
  reports is not evidence of safety.
- Only the **first** device on each report is mapped; a report naming several devices shows one.
- Dates arrive as `YYYYMMDD` **strings**, as the FDA publishes them, and are not reformatted here.
- openFDA rate-limits; large sweeps are paced.

### Inputs

| Input | Type | Default | What it does |
|---|---|---|---|
| `search` | string | — | openFDA search syntax, e.g |

Stops after **1000 rows** or **5 requests**, whichever comes first — raise
`maxItems` and `maxPages` for more. Requests are paced 200 ms apart, and pages are fetched by offset (100 at a time).

The dataset's SUMMARY records `truncated` and `stopReason`, so a run that hit a cap says so
rather than looking like a source that had nothing more.

### Pricing

Pay per result.

### Fields

| Field | Type | What it holds |
|---|---|---|
| `reportNumber` | number | Regulator's identifier for this report. Use it to cite or de-duplicate. |
| `eventType` | string | Type of event as the regulator categorises it. Event types do not indicate severity. |
| `dateReceived` | string | Date the regulator received the report, as opposed to the date the event happened. |
| `dateOfEvent` | string | Date the event happened, as reported. Often approximate, and sometimes after the report was received. |
| `deviceBrandName` | string | Brand name of the device, as the manufacturer markets it. |
| `deviceGenericName` | string | Generic or common name of the device. |
| `deviceClass` | string | Regulatory risk class of the device. A NUMBER in regulatory documents (1, 2, 3), where 3 is highest risk. |
| `manufacturer` | string | Name of the manufacturing organisation as reported. Free text, and not matched to any register, so the same firm appears under several spellings. |
| `manufacturerCity` | string | City the device manufacturer reports being in. |
| `manufacturerState` | string | State or region the device manufacturer reports being in. Usually a two-letter US state code. |

# Actor input Schema

## `search` (type: `string`):

openFDA search syntax, e.g. device.brand_name:"PUMP" or event_type:Injury.

## `maxItems` (type: `integer`):

Stop after this many rows.

## `maxPages` (type: `integer`):

Stop after this many pages.

## Actor input object example

```json
{
  "maxItems": 500,
  "maxPages": 5
}
```

# Actor output Schema

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

One row per item, with the 10 fields listed under Views.

# 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 = {
    "maxItems": 500,
    "maxPages": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/openfda-device-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 = {
    "maxItems": 500,
    "maxPages": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/openfda-device-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 '{
  "maxItems": 500,
  "maxPages": 5
}' |
apify call alaudinburki/openfda-device-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/openfda-device-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/2In83cNvrXd3uKAnt/builds/cZcVsWRdKF436KrMP/openapi.json