# Monitor FDA 510(k) device clearances

**Use case:** 

Track recent FDA 510(k) medical device clearances from openFDA by device keyword or applicant. Stay ahead of competitor clearances, predicate devices, and market-entry signals in MedTech.

## Input

```json
{
  "deviceName": "continuous glucose",
  "maxItems": 25
}
```

## Output

```json
{
  "kNumber": {
    "label": "K Number"
  },
  "deviceName": {
    "label": "Device Name"
  },
  "applicant": {
    "label": "Applicant"
  },
  "decisionDate": {
    "label": "Decision Date"
  },
  "decisionCode": {
    "label": "Decision Code"
  },
  "productCode": {
    "label": "Product Code"
  },
  "advisoryCommittee": {
    "label": "Advisory Committee"
  },
  "sourceUrl": {
    "label": "Source Url"
  }
}
```

## About this Actor

This example demonstrates how to use [FDA 510k Device Clearance Monitor](https://apify.com/technicaldost/fda-device-510k-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/technicaldost/fda-device-510k-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/technicaldost/fda-device-510k-monitor.md

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`).