device510k: the structured clearance records — device name and class, product code, applicant, decision code and date, advisory committee, and regulation number.device510k-summaries: the 510(k) summary PDFs behind those clearances, with per-page extracted text, so you can search the actual submission content, not just the metadata.
Each dataset requires its own Evidence scope. See the Evidence overview for how scopes work.
Search clearances
results includes title, statementOrSummary, summaryText, kNumbersMentioned, a device object (kNumber, tradeName, deviceName, deviceClass, productCode, clearanceType, regulationNumber, medicalSpecialtyDescription), a decision object (decisionCode, decisionDescription, decisionDate, advisoryCommittee, expeditedReviewFlag), and applicantInformation.
s accepts _relevance (default), device.device_class, device.date_received, and decision.decision_date.
Search summary PDFs
filename and attachments; each attachment carries pages with extracted text (content), page counts, file metadata, and ontology tags/categories. Use this when the question is about what a submission actually says — predicate device claims, testing summaries, intended use — rather than the clearance metadata.
Single record
GET /api_partner/evidence/device510k/{device_id} and GET /api_partner/evidence/device510k-summaries/{item_id} return one full record each.
Common uses
- Predicate research: search summaries for a device type to find the predicate chains competitors cite;
kNumbersMentionedon clearance records links related submissions. - Regulatory watch: sort clearances by
decision.decision_dateand filter by product code or advisory committee to monitor a device category. - Full safety picture: combine with MAUDE adverse-event reports for post-market signals on the same devices.
