FDA medical device marketing decisions: 510(k) clearances and PMA approvals with supplements, by applicant, product code, device name and decision date, newest first.
curl -X POST "https://api.primaryapi.com/v1/run/fda.device_clearances" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"pathway":"510k","number":"K263860","dateFrom":"2026-10-30","dateTo":"2026-10-30"}'{
"output": {
"found": true,
"data": {
"nextCursor": null,
"decisions": [
{
"thirdPartyReview": true,
"pathway": "510k",
"number": "K263860",
"supplementNumber": null, …
}
]
}
},
"credits": 1
}Input and output
9 fields
510k.K263860.2026-10-30.2026-10-30.22 fields
Good to know
FDA device decisions, refreshed weekly.
Newest decision date first. Ties by number then supplement, so the order is stable between runs.
Filters combine with AND.
Without dateFrom the window is the 90 days up to dateTo (default today, UTC). The response hint says so.
For a monitor, pin dateFrom to a fixed date (for example the day you create it). The output then changes only when a record is added or updated, never because an old one ages out of a rolling window.
Paging stops after 25,000 records per pathway.
More from FDA. Same key, same credits.
The same key and credits work for every API.