# openFDA Device Leads Feed (`solid_chafer/openfda-device-leads`) Actor

Free feed of new FDA medical-device 510(k) clearances, device listings and recalls from the public-domain openFDA API, one lead row per company. Not affiliated with FDA. Built with AI assistance.

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

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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 Leads Feed — new FDA device clearances, listings & recalls as sales leads

Get a fresh list of medical-device companies that **just did something at the FDA**: cleared a 510(k), listed a new device, or posted a recall. Each one is a company that may need your help now (contract manufacturing, sterilization, distribution, regulatory, quality, legal, or recall logistics).

### What you get (one row per lead)

| Field | Meaning |
|---|---|
| leadType | `510k_clearance`, `new_device_listing`, or `recall` |
| company, contactName, phone, address, state | as filed with FDA (510(k) contacts may be the submitter's consultant) |
| device, productCode, establishmentType | what the event is about |
| date, dateType | decision date / listing created date / recall posted date |
| recallReason, recallStatus | recalls only |
| sourceUrl, apiUrl | link to the FDA record and the openFDA query |

### Input

Date range, sources, FDA product codes and/or device keywords, US state, max results. Example:

```json
{"dateFrom":"2026-09-01","dateTo":"2026-10-27","sources":["510k","recall"],"state":"CA","productCodes":["QJP"],"maxResults":200}
```

Schedule it weekly with a 7-day window to get a recurring lead feed.

### Cost

This actor is free. You pay only the normal Apify platform usage for your runs, which is small.

### Data source & disclosures

- Data comes from the U.S. FDA's **openFDA API** (510(k), device registration & listing, device recall endpoints). openFDA data is public domain / CC0. The actor calls the official API and does no website scraping.
- **Not affiliated with or endorsed by the FDA.** openFDA warns its data is unvalidated. Verify before relying on it. Not regulatory or legal advice.
- FDA publishes 510(k) decisions and listings with a lag of about a week. Recent days may be incomplete.
- openFDA caps paging at 25,000 records per query. Narrow the dates or product codes for bigger pulls.
- **AI-assisted build:** this actor and its README were built with AI assistance and reviewed by the publisher.

# Actor input Schema

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

YYYY-MM-DD (510k decision date / listing created / recall posted)

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

YYYY-MM-DD

## `sources` (type: `array`):

Any of: 510k, registrationlisting, recall

## `productCodes` (type: `array`):

e.g. QJP, DXN. Empty = all

## `keywords` (type: `array`):

Matched against device name / description

## `state` (type: `string`):

2-letter code, e.g. CA

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

Maximum rows to return.

## `fdaApiKey` (type: `string`):

Only raises rate limits

## Actor input object example

```json
{
  "dateFrom": "2026-09-01",
  "dateTo": "2026-10-27",
  "sources": [
    "510k",
    "registrationlisting",
    "recall"
  ],
  "maxResults": 100
}
```

# Actor output Schema

## `leads` (type: `string`):

No description

# 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("solid_chafer/openfda-device-leads").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("solid_chafer/openfda-device-leads").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 solid_chafer/openfda-device-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,solid_chafer/openfda-device-leads"
        }
    }
}
```

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/EhID7A6OgzeysR3xP/builds/YX9CbKMFX2RSx2wtB/openapi.json