POST /api/dailymed/labels
Price: 10 credits
Get a DailyMed drug label by its SPL set id
Resolves one DailyMed SPL set id to the full label: the prescribing-information sections with their LOINC codes, the text of each, the tables as rows, the marketed products with their NDC codes, ingredients and package hierarchy, the manufacturing establishments and the label images. Kit components ship as products of their own, linked by `kit_ndc_product_code`; one the label gives no NDC of its own has a null `ndc_product_code` and is identified by name, dosage form and ingredients. The `label_title` field is the short catalogue title ('DUPIXENT (DUPILUMAB) INJECTION, SOLUTION [SANOFI-AVENTIS U.S. LLC]'); `document_title` is the label's own heading, which on a prescription label is the whole Highlights preamble. Section text is plain text with the tables lifted out into `tables`, so read a dosage or adverse-reaction grid there rather than from `text`. A tablet's colour, shape, size, score and imprint are in each product's characteristics, which is what identifies a loose pill.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)setid string required — DailyMed SPL set id (UUID), or a DailyMed drugInfo URL containing it (examples: "595f437d-2729-40bb-9c62-c8ece1f82780", "https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=595f437d-2729-40bb-9c62-c8ece1f82780"; minLength: 1)@type string (default: "DailymedLabel")setid string requireddocument_id string nullableversion integer nullablelabel_title string nullabledocument_title string nullabledocument_type string nullabledocument_type_code string nullablepublished_at integer nullableeffective_at integer nullablelabeler string nullablelabeler_duns_number string nullableproducts array (default: [])@type string (default: "DailymedProduct")ndc_product_code string nullablename string nullablegeneric_name string nullabledosage_form string nullableroute string nullablemarketing_category string nullableapplication_number string nullablemarketing_status string nullablemarketing_start_at integer nullablemarketing_end_at integer nullablecombination_product_type string nullabledea_schedule_code string nullabledea_schedule string nullablekit_ndc_product_code string nullablequantity_in_kit string nullablecharacteristics array (default: [])@type string (default: "DailymedProductCharacteristic")code string requiredvalue string requiredingredients array (default: [])@type string (default: "DailymedIngredient")name string requiredunii string nullablestrength string nullableis_active boolean (default: false)active_moiety string nullablepackages array (default: [])@type string (default: "DailymedPackage")ndc string requiredpackage_type string nullablequantity string nullablemarketing_status string nullablemarketing_start_at integer nullablemarketing_end_at integer nullablepackages array (default: [])establishments array (default: [])@type string (default: "DailymedEstablishment")name string requiredduns_number string nullableoperations array (default: [])ndc_product_codes array (default: [])sections array (default: [])@type string (default: "DailymedSection")code string requiredname string nullableheading string nullabletext string nullablehighlight string nullabletables array (default: [])@type string (default: "DailymedTable")caption string nullableheaders array (default: [])rows array (default: [])footers array (default: [])image_names array (default: [])sections array (default: [])images array (default: [])@type string (default: "DailymedImage")name string requiredurl string requiredmime_type string nullabledescription string nullableweb_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 — Label not found 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.