All sources

openFDA 510(k) decisions

Build a pipeline

Date-window pages of FDA 510(k) decisions with device, applicant, decision and classification fields, explicit pagination and De Novo exclusion counts.

How a pipeline uses this source

SourcesClearances — Date-window pages of FDA 510(k) decisions with device, applicant, decision and classification fields, explicit pagination and De Novo exclusion counts.
Step
Clearances
Date-window pages of FDA 510(k) decisions with device, applicant, decision and classification fields, explicit pagination and De Novo exclusion counts.
Start
Checks — 2 saved checks run against the live site and a stored copy of the page. Last passed 1 Nov 2026. When the site changes, Jason repairs the source and publishes a new revision.
Step
Checks
2 saved checks run against the live site and a stored copy of the page. Last passed 1 Nov 2026. When the site changes, Jason repairs the source and publishes a new revision.
Your Dataset — Rows delivered to your sheet, warehouse, alerts or assistant on the schedule you choose.
Output
Your Dataset
Rows delivered to your sheet, warehouse, alerts or assistant on the schedule you choose.
End
Sources — fda.gov
Sources
fda.gov
  1. 01 · sources

    Sources

    fda.gov

  2. 02

    Clearances

    Date-window pages of FDA 510(k) decisions with device…

  3. 03

    Checks

    2 saved checks run against the live site and a stored copy of…

  4. 04 · output

    Your Dataset

    Rows delivered to your sheet, warehouse, alerts or assistant…

What openFDA 510(k) decisions does

Date-window pages of FDA 510(k) decisions with device, applicant, decision and classification fields, explicit pagination and De Novo exclusion counts.

Collects: Date-window pages of FDA 510(k) decisions

Reads

api.fda.gov

Limitations

One live API page, not an exhaustive archive or medical advice. Source totals include excluded De Novo records. API 404/no-match, rate limits and other errors propagate; never treated as a successful empty result. Maximum 100 records and skip 25000; narrower date windows needed beyond API offset range. Source may revise history.

Site and app names identify the source only. Jsonify is not affiliated with or endorsed by them. How Jsonify reads sites, and how a site owner can opt out: for site owners.

Need something different?

Describe it. Get verified rows, kept current.

Migrate from your current tool

Share what you run on your current tool today. Jason, Jsonify’s AI data engineer, reads it and proposes the same pipelines on Jsonify, with checks and repairs built in.

Don’t include passwords or API keys. Exports, task configs and screenshots can be attached in Jsonify on the next step. Privacy

Connect your data assistant

Build datasets and work with your data in Claude, ChatGPT, Copilot or another assistant.

Connect in Claude

  1. Open the Jsonify connector: Open on Claude.ai ↗
  2. Select Connect and sign in to Jsonify.
  3. In a chat, enable Jsonify under + → Connectors and describe the data you need.
Advanced

Team or Enterprise account? Your workspace owner enables Jsonify once for everyone from Admin settings → Connectors. Jsonify is a community connector in the directory — some admins allow those by default, some review them first.

No directory? Add it by hand: Settings → Connectors → + Add custom connector, name it Jsonify, paste the server URL below, then Connect.

Server URLhttps://factory.jsonify.com/mcp

Official Claude custom-connector guide ↗

Then say: “build me a dataset of competitor product prices and availability, refreshed daily”. Full instructions per client on /connect.