/openfda/drug/enforcement/search

POST /api/openfda/drug/enforcement/search

Price: 5 credits

Search FDA drug recall enforcement reports by firm, classification, status, location and date

How to use it

Search FDA drug recall enforcement reports. Combine a free-text keyword with structured filters — recalling firm, recall classification, status, product description, reason for recall, state, country, voluntary/mandated flag, and initiation- or report-date ranges. Each result is a full recall report (same shape as the enforcement 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 recall fields (examples: "sterility")
• recalling_firm string nullable — Recalling firm name (examples: "Albek De Mexico")
• classification string nullable — Recall classification (one of: "Class I", "Class II", "Class III")
• status string nullable — Recall status (one of: "Ongoing", "Completed", "Terminated", "Pending")
• product_description string nullable — Text in the recalled product description (examples: "hand sanitizer")
• reason_for_recall string nullable — Text in the reason for recall (examples: "contamination")
• state string nullable — Recalling firm US state code (examples: "IL")
• country string nullable — Recalling firm country (examples: "United States")
• voluntary_mandated string nullable — Whether the recall was voluntary or FDA mandated (one of: "Voluntary: Firm initiated", "FDA Mandated")
• initiation_from string nullable — Recall initiation date from (YYYY-MM-DD); requires initiation_to
• initiation_to string nullable — Recall initiation date to (YYYY-MM-DD); requires initiation_from
• report_from string nullable — Report date from (YYYY-MM-DD); requires report_to
• report_to string nullable — Report date to (YYYY-MM-DD); requires report_from
• count integer required — Number of recall reports to return (min: 1)

Response

• @type string (default: "OpenfdaDrugEnforcement")
• recall_number string required
• event_id string nullable
• status string nullable
• classification string nullable
• product_type string nullable
• recalling_firm string nullable
• address_1 string nullable
• address_2 string nullable
• city string nullable
• state string nullable
• postal_code string nullable
• country string nullable
• voluntary_mandated string nullable
• initial_firm_notification string nullable
• distribution_pattern string nullable
• product_description string nullable
• product_quantity string nullable
• reason_for_recall string nullable
• code_info string nullable
• recall_initiation_at integer nullable
• center_classification_at integer nullable
• report_at integer nullable
• termination_at integer 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: [])

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.