# FDA 510(k) Clearance & Decision Monitor (`maydit/fda-device-clearance-monitor`) Actor

Monitor FDA 510(k) decisions by K number, product code or applicant. Export company and device details, source update dates and saved changes from the monthly public dataset.

- **URL**: https://apify.com/maydit/fda-device-clearance-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** News, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 saved observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 510(k) Clearance & Decision Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/fda-device-clearance-monitor-5be5f4f10d5b.png)

## FDA 510(k) Clearance & Decision Monitor

Turn the monthly public FDA 510(k) decision dataset into a small, traceable research window or an exact device-decision watchlist. Each saved observation includes the K number, device and applicant names, product code, decision date, source update date and official record link. Optional comparisons show the source fields that changed between complete observations.

### Start with three records

Run the default input to retrieve three substantial-equivalence decisions, sorted by source decision date. No new API key, login, proxy or paid source subscription is required for the bounded queries tested here. The public API has shared IP quotas and may temporarily reject or limit requests.

```json
{
  "maxResults": 3,
  "clearanceOnly": true,
  "comparePrevious": false
}
```

This is **monthly FDA data**, not a real-time device launch, availability or sales feed. `sourceDataLastUpdated` comes directly from the source metadata; `observedAt` is when this Actor read it. `sourceDataAgeDays` and `sourceFreshness` make aged source data visible. The 45-day label is a transparent observation threshold, not an FDA service guarantee. Decision-date ties retain source ordering, so a small discovery window can change membership without a new decision.

### Three useful recipes

#### Review three FDA clearance decisions

Inspect a bounded decision-date-sorted window of three SESE records and the monthly source update date.

```json
{
  "maxResults": 3,
  "clearanceOnly": true,
  "comparePrevious": false
}
```

#### Track two exact device decisions

Compare source fields for two exact K-number records without inferring current device availability.

```json
{
  "kNumbers": [
    "K260648",
    "K263232"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "device-decision-watchlist"
}
```

#### Find GWL product-code decisions

Review three substantial-equivalence records for FDA product code GWL, preserving applicant and source identity.

```json
{
  "productCodes": [
    "GWL"
  ],
  "maxResults": 3,
  "clearanceOnly": true,
  "comparePrevious": false
}
```

Use `kNumbers` for up to 20 exact decisions. Exact IDs override discovery filters; the source request includes every selected ID even if your output cap is smaller. Missing IDs appear in `SUMMARY.notFoundKNumbers` without billable placeholder rows. Discovery supports up to five three-letter `productCodes`, an optional `applicantPhrase`, and `clearanceOnly`. Applicant phrase matching uses the source search index and does not establish a corporate identity match. Turning off `clearanceOnly` includes other recorded 510(k) decision codes.

### What the fields mean

| Field | Interpretation |
| --- | --- |
| `kNumber`, `recordId`, `sourceUrl` | Exact FDA submission identity and official record link. |
| `deviceName`, `applicantName`, `productCode` | Published device, applicant and product-code labels. |
| `decisionCode`, `decisionDescription`, `decisionDate` | The recorded 510(k) decision and date, not current market status. |
| `clearanceRecorded` | True for documented substantial-equivalence codes SEKD, SESD, SESE, SESK, SESP and SESU; null for other codes. This is not PMA approval. |
| `deviceClass`, `regulationNumber` | Optional classification harmonization from openFDA; singular values only when unambiguous. All source values are retained in deviceClasses and regulationNumbers, not a unique manufacturer linkage. |
| `receivedDate`, `clearanceType`, `statementOrSummary` | Source administrative fields; missing values remain null. |
| `sourceDataLastUpdated`, `sourceCadence`, `observedAt` | Source update date, monthly cadence and separate retrieval time. |
| `comparisonStatus`, `changedFields`, `previous` | New, changed or unchanged observed source fields when comparison is requested. |

Applicant city/state/country are business-location labels from the record. No personal contact names, street addresses, emails, FEI/registration arrays, GMDN terms or raw source document are exported. No clearance amount, revenue, efficacy endorsement, procurement demand or buying-intent score is invented. `currentMarketAvailability` always remains `not_determined`. Do not use openFDA data to make medical-care decisions.

### Saved changes and honest coverage

Run the same selection and `snapshotName` sequentially with `comparePrevious:true`. The first run is a baseline. `onlyChanges:true` also enables comparison and can correctly save zero records on an unchanged repeat. Source-wide metadata refreshes and ordinary passage of time do not themselves generate changed records. Record corrections are observed differences, not necessarily newly issued decisions.

History uses the named `fda-device-clearance-monitor-history` key-value store and scope-specific keys. Only positive observed records are retained. Missing or no-longer-selected records are never classified as withdrawn, recalled or removed. A source failure, exhausted charge allowance, interrupted output or deadline prevents the entire run from advancing its baseline. Concurrent writers are detected; run each snapshot sequentially.

`SUMMARY.selectedWindowComplete` covers the requested selection; `sourceUniverseComplete` indicates whether the response reports more matches outside that window. A complete selected window can have `incomplete:false` and `sourceUniverseComplete:false`. An exact source `NOT_FOUND` response is an empty query result, not proof that a clearance never existed or was withdrawn. A failed or malformed response fails visibly instead of creating a paid diagnostic row. HTTP denials and rate limits are not bypassed or repeatedly retried.

### Pricing and bounds

Standard event pricing is **$0.002 per confirmed saved observation**, plus **$0.00005 Actor Start**. Three observations total $0.00605 in Actor event charges; 100 total $0.20005. Plan discounts and applicable Apify platform charges are separate. Unchanged-only runs can have zero result charges while still incurring start/platform usage. Reports and source diagnostics are not billed as dataset observations. Set Run options' maximum total charge to bound spending.

Default output is three records, maximum 100. The one source request is capped at 20 seconds and 6 MiB with public-address validation and no redirects. The default whole-run budget is 60 seconds, allowed 30–120; the platform timeout may stop sooner. The unauthenticated public API's documented quotas are shared by IP; this Actor does not accept an API key or raise source limits.

### Outputs and source

Download the dataset as JSON or CSV. `SUMMARY` records selected coverage, source age, errors and baseline status; `RUN_REPORT` provides a readable report without extra paid rows. Use your own Apify saved task or API client for repeated observations. This Actor does not schedule itself, contact applicants or make purchases.

[Official 510(k) API](https://open.fda.gov/apis/device/510k/) · [Searchable fields](https://open.fda.gov/apis/device/510k/searchable-fields/) · [API limits](https://open.fda.gov/apis/authentication/) · [openFDA terms](https://open.fda.gov/terms/).

Independent of the FDA and not endorsed by it. Source data may be delayed, corrected or incomplete. Review the official record before using an observation in a business or regulatory workflow. Report reproducible issues through this Actor's Issues tab with a non-sensitive input and run link.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [FDA Recalls Scraper - Drug, Device & Food](https://apify.com/maydit/us-fda-recalls-scraper)

Review device recall records alongside a manually matched clearance or decision record.

1. Verify the manufacturer and exact product identity before configuring a separate device-recall search.
2. Preserve K numbers and recall IDs as different identifiers, along with their source dates and scope.

A clearance record does not establish safety, current sale status or recall absence. Name similarity alone is not a verified product match.

#### [FDA Warning Letter Monitor - Supplier & Closeout Changes](https://apify.com/maydit/fda-warning-letter-monitor)

Add official inspection and warning-letter context when researching a device applicant or manufacturer.

1. Independently verify the legal organization, facilities and names relevant to a device record.
2. Configure a separate warning-letter review and retain the original letter dates and cited activities.

A matching organization name does not establish that a letter concerns the device, and no letter result is not evidence of compliance. This is research context, not a medical or regulatory determination.

# Actor input Schema

## `kNumbers` (type: `array`):

Up to 20 exact K numbers, for example K260648. Overrides product, applicant and clearance filters. Missing records are reported without being declared removed.

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

Up to five three-letter codes, for example GWL. Discovery requires each result to match one selected code. Ignored when exact K numbers are supplied.

## `applicantPhrase` (type: `string`):

Optional literal phrase in the FDA applicant index, up to 120 characters. This is source search, not verified corporate identity. Quotes and backslashes are not accepted. Ignored for exact K numbers.

## `clearanceOnly` (type: `boolean`):

Discovery includes decision_code SESE by default. Turning off includes other 510(k) decision codes. This is not PMA approval, efficacy, market availability or a purchase signal. Ignored for exact K numbers.

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

1–100. Discovery requests one decision-date-sorted window of this size. An exact watchlist larger than this output cap is incomplete and cannot advance history.

## `maxRunSeconds` (type: `integer`):

30–120 seconds including source, output and history. The public API request is bounded to 20 seconds and the platform timeout may stop earlier.

## `comparePrevious` (type: `boolean`):

Compare source decision, applicant and device fields with a previous complete observation of the same scope. First run establishes a baseline.

## `onlyChanges` (type: `boolean`):

Enables comparison and may correctly save zero rows on an unchanged repeat. Missing records do not imply withdrawal or market removal.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. Selection filters also separate history. Run each snapshot sequentially.

## Actor input object example

```json
{
  "kNumbers": [],
  "productCodes": [],
  "applicantPhrase": "",
  "clearanceOnly": true,
  "maxResults": 3,
  "maxRunSeconds": 60,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (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 = {
    "clearanceOnly": true,
    "maxResults": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/fda-device-clearance-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 = {
    "clearanceOnly": True,
    "maxResults": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/fda-device-clearance-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 '{
  "clearanceOnly": true,
  "maxResults": 3
}' |
apify call maydit/fda-device-clearance-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/fda-device-clearance-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/eSEsqIXQh6fhJI6Ln/builds/cYjxk3sPQcGnZ8eSG/openapi.json
