POST /api/openfda/drug/events/search
Price: 5 credits
Search FDA FAERS drug adverse-event reports by drug, reaction, seriousness, sex and date
Search the FDA Adverse Event Reporting System (FAERS). Combine a free-text keyword with structured filters — medicinal product, suspect drug generic or brand name, reported reaction (MedDRA term), the serious flag, death outcome, patient sex, country of occurrence and a received-date range. Each result is a full FAERS safety report (same shape as the events endpoint).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string nullable — Free-text query across all report fields (examples: "nausea")medicinal_product string nullable — Reported medicinal product name (examples: "BONIVA")generic_name string nullable — Suspect drug generic name (examples: "ibandronate")brand_name string nullable — Suspect drug brand name (examples: "Boniva")reaction string nullable — Reported reaction (MedDRA preferred term) (examples: "Headache")serious boolean nullable — Only serious (or non-serious) reportsseriousness_death boolean nullable — Only reports where the outcome was deathsex string nullable — Patient sex (one of: "Male", "Female")country string nullable — Country where the event occurred (examples: "US")received_from string nullable — Report received date from (YYYY-MM-DD); requires received_toreceived_to string nullable — Report received date to (YYYY-MM-DD); requires received_fromcount integer required — Number of adverse-event reports to return (min: 1)@type string (default: "OpenfdaDrugEvent")safetyreportid string requiredsafetyreportversion string nullableserious boolean (default: false)seriousness array (default: [])received_at integer nullablereceipt_at integer nullabletransmission_at integer nullablereport_type string nullablefulfill_expedite_criteria string nullablecompany_number string nullableoccur_country string nullableprimary_source_country string nullablereporter_country string nullablereporter_qualification string nullablesender_organization string nullablepatient object nullable@type string (default: "OpenfdaEventPatient")onset_age string nullableonset_age_unit string nullablesex string nullableweight string nullablereactions array (default: [])@type string (default: "OpenfdaEventReaction")term string requiredoutcome string nullabledrugs array (default: [])@type string (default: "OpenfdaEventDrug")medicinal_product string nullablecharacterization string nullableindication string nullableadministration_route string nullableauthorization_number string nullabledosage_text string nullablestart_at integer nullableopenfda 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 nullabledevice_name string nullablemedical_specialty_description string nullableregulation_number string nullablefei_number array (default: [])registration_number array (default: [])k_number array (default: [])pma_number array (default: [])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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.