/openfda/device/clearances/search

POST /api/openfda/device/clearances/search

Price: 10 credits

Search FDA 510(k) device clearances by applicant, device, product code, class and date

How to use it

Search FDA 510(k) device clearances. Combine a free-text keyword with structured filters — applicant, device name, product code, decision code, clearance type, advisory committee, state, country, device regulatory class, and a decision-date range. Each result is a full clearance record (same shape as the clearances endpoint).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Free-text query across all clearance fields (examples: "catheter")
• applicant string nullable — Applicant company name (examples: "Novametrix")
• device_name string nullable — Device name (examples: "ventilator")
• product_code string nullable — FDA product code (examples: "BZD")
• decision_code string nullable — Decision code (examples: "SESE")
• clearance_type string nullable — Clearance type (examples: "Traditional", "Special")
• advisory_committee string nullable — Advisory committee code (examples: "AN", "OP")
• state string nullable — Applicant US state code (examples: "IL")
• country_code string nullable — Applicant country code (examples: "US")
• device_class string nullable — Device regulatory class (one of: "1", "2", "3", "U", "N", "F")
• decision_from string nullable — Decision date from (YYYY-MM-DD); requires decision_to
• decision_to string nullable — Decision date to (YYYY-MM-DD); requires decision_from
• count integer required — Number of clearances to return (min: 1)

Response

• @type string (default: "OpenfdaDeviceClearance")
• k_number string required
• applicant string nullable
• device_name string nullable
• product_code string nullable
• decision_code string nullable
• decision_description string nullable
• clearance_type string nullable
• advisory_committee string nullable
• advisory_committee_description string nullable
• review_advisory_committee string nullable
• decision_at integer nullable
• date_received_at integer nullable
• contact string nullable
• address_1 string nullable
• address_2 string nullable
• city string nullable
• state string nullable
• country_code string nullable
• zip_code string nullable
• postal_code string nullable
• statement_or_summary string nullable
• third_party_flag boolean nullable
• expedited_review_flag boolean nullable
• openfda object nullable
  • @type string (default: "OpenfdaBlock")
  • application_number array (default: [])
  • brand_name array (default: [])
  • generic_name array (default: [])
  • manufacturer_name array (default: [])
  • product_ndc array (default: [])
  • package_ndc array (default: [])
  • product_type array (default: [])
  • route array (default: [])
  • substance_name array (default: [])
  • rxcui array (default: [])
  • unii array (default: [])
  • spl_id array (default: [])
  • spl_set_id array (default: [])
  • nui array (default: [])
  • pharm_class_cs array (default: [])
  • pharm_class_epc array (default: [])
  • pharm_class_moa array (default: [])
  • pharm_class_pe array (default: [])
  • is_original_packager array (default: [])
  • device_class string nullable
  • device_name string nullable
  • medical_specialty_description string nullable
  • regulation_number string nullable
  • fei_number array (default: [])
  • registration_number array (default: [])
  • k_number array (default: [])
  • pma_number array (default: [])
• web_url string (default: "")

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.