May’d It
FDA 510(k) Clearance & Decision Monitor — illustrative workflow

DATA TOOLS / health

FDA 510(k) Clearance & Decision Monitor

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.

JSON / CSV outputLimited permissionsSource: maydit/fda-device-clearance-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

Medical-device market research, regulatory intelligence, supplier mapping and business-development teams reviewing publicly recorded FDA decisions.

titlekNumberapplicantNameproductCodedecisionDescriptionclearanceRecordeddecisionDatedeviceClassregulationNumber

Which device decisions and applicant records changed in FDA 510(k) data?

Choose a small product-code or applicant search window and review the FDA decision date and monthly source update. Verify the applicant and K-number on the official FDA record before adding it to a research shortlist. Save exact K numbers to a sequential watchlist and compare observed source changes.

Check the fit and source limits

Monthly public data, not live market availability or a launch feed. SESE substantial-equivalence clearance is distinct from PMA approval and does not establish efficacy. Applicant names are source labels; no revenue, buying intent, email or personal contact enrichment. A bounded window is not complete coverage of all FDA decisions.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-11-16. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "recordId": "fda510k:K260648",
  "title": "PolySense",
  "kNumber": "K260648",
  "applicantName": "Itamar Medical , Ltd.",
  "productCode": "GWL",
  "decisionDescription": "Substantially Equivalent",
  "clearanceRecorded": true,
  "decisionDate": "2026-10-30",
  "deviceClass": "2",
  "regulationNumber": "882.1835",
  "sourceDataLastUpdated": "2026-11-02",
  "sourceFreshness": "updated_within_45_days",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm?ID=K260648"
}

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: aBKhpDU8OP21nane4. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

Historical evidence for this exact JSON was recorded 2026-11-16 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "maxResults": 3,
  "clearanceOnly": true,
  "comparePrevious": false
}
Download input.json

CHOOSE A STARTING POINT

3 ready-to-use inputs

Pick a focused example, copy or download its JSON, then review the inputs and current pricing in your own Apify account. Downloading a configuration does not start a run.

Default input · Input schema · Saved output capture

Review three FDA clearance decisions

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

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

Saved run evidence: 2026-11-16 UTC · 3 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Track two exact device decisions

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

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

Saved run evidence: 2026-11-16 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Find GWL product-code decisions

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

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

Saved run evidence: 2026-11-16 UTC · 3 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Download all example inputs and evidence references

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
kNumbersarray

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

productCodesarray

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.

applicantPhrasestring

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.

clearanceOnlyboolean

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.

maxResultsinteger

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.

maxRunSecondsinteger

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

comparePreviousboolean

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

onlyChangesboolean

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

snapshotNamestring

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

Output fields

titlekNumberapplicantNameproductCodedecisionDescriptionclearanceRecordeddecisionDatedeviceClassregulationNumbersourceDataLastUpdatedsourceFreshnesscomparisonStatussourceUrl

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Saved observation$0.002One validated observation confirmed saved to the dataset.

Check current Apify pricing ↗ before running.

Use with an AI agent or API

Connect this Actor through MCP

Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the official configurator provides client-specific instructions.

{
  "mcpServers": {
    "maydit": {
      "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/fda-device-clearance-monitor"
    }
  }
}

Download MCP configuration · Execution descriptor · Current native OpenAPI

Ask the agent to inspect maydit/fda-device-clearance-monitor (Actor ID eSEsqIXQh6fhJI6Ln) with fetch-actor-details, including input, output and pricing. Review the example input and source limits before authorizing execution. For call-actor, place a maximum charge of $0.05 and timeout of 300 seconds in callOptions, not the Actor input. A spending cap can stop a run before its intended scope completes.

After starting once, keep the returned run ID. Use get-actor-run for status, get-key-value-store-record for that run's SUMMARY, and get-dataset-items with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.

Supply your own credentials

For direct API use, set APIFY_TOKEN securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.

This input schema has no source-credential fields. Apify authorization is still required to start a paid run.

Start once, then retrieve the same run

Download run-actor.mjs, execution.json and input.json into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.

# Preview only: makes no requests
node run-actor.mjs

# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run

# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run

The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.

It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.

Review run-status.json, summary.json, items.json and download-receipt.json. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.

For a custom integration, use the same sequence:

  1. POST https://api.apify.com/v2/actors/eSEsqIXQh6fhJI6Ln/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS with a JSON input body and Bearer authorization. Save data.id once.
  2. GET https://api.apify.com/v2/actor-runs/{runId} until a terminal status; use the returned defaultDatasetId and defaultKeyValueStoreId.
  3. GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY; interpret diagnostics using this Actor's coverage guide.
  4. GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100; paginate the same completed dataset and retain source URLs/timestamps.

The official run API, dataset pagination documentation and MCP guide describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.

BUILD A REVIEWED WORKFLOW

Use this with companion tools

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

Parallel research context

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.

Read the companion guide →

Parallel research context

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.

Read the companion guide →

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Source contract captured from build 1.0.1. Presentation refreshed 2026-11-16. Example outputs retain their original sample context; they are not live results.

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.

{
  "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.

{
  "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.

{
  "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.

{
  "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 · Searchable fields · API limits · openFDA 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

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

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.