POST /api/openfda/drug/ndc/search
Price: 5 credits
Search the FDA National Drug Code (NDC) directory by name, NDC, form, route and category
Search the FDA National Drug Code (NDC) directory. Combine a free-text keyword with structured filters — brand name, generic name, labeler, product NDC, dosage form, route, marketing category, product type, pharmacologic class and the finished flag. Each result is a full NDC product record (same shape as the ndc 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 NDC fields (examples: "ibuprofen")brand_name string nullable — Brand (proprietary) name (examples: "XTRA")generic_name string nullable — Generic name (examples: "Benzalkonium Chloride")labeler_name string nullable — Labeler (company) name (examples: "Pfizer")product_ndc string nullable — Product NDC code (examples: "85212-0040")dosage_form string nullable — Dosage form (examples: "TABLET", "LOTION")route string nullable — Route of administration (examples: "ORAL", "TOPICAL")marketing_category string nullable — Marketing category (examples: "ANDA", "OTC MONOGRAPH DRUG")product_type string nullable — Marketing product type (one of: "HUMAN PRESCRIPTION DRUG", "HUMAN OTC DRUG", "NON-STANDARDIZED ALLERGENIC", "STANDARDIZED ALLERGENIC", "PLASMA DERIVATIVE", "VACCINE", "CELLULAR THERAPY")pharm_class string nullable — Pharmacologic class (examples: "Vitamin C [EPC]")finished boolean nullable — Only finished (marketed) or unfinished productscount integer required — Number of NDC products to return (min: 1)@type string (default: "OpenfdaDrugNdc")product_ndc string requiredproduct_id string nullablespl_id string nullablebrand_name string nullablebrand_name_base string nullablegeneric_name string nullablelabeler_name string nullabledosage_form string nullableroute array (default: [])marketing_category string nullableproduct_type string nullableapplication_number string nullablefinished boolean (default: false)marketing_start_at integer nullablemarketing_end_at integer nullablelisting_expiration_at integer nullablepharm_class array (default: [])active_ingredients array (default: [])@type string (default: "OpenfdaNdcActiveIngredient")name string requiredstrength string nullablepackaging array (default: [])@type string (default: "OpenfdaNdcPackage")package_ndc string requireddescription string nullablemarketing_start_at integer nullablemarketing_end_at integer nullablesample boolean (default: false)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 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: [])web_url string (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.