/goodrx/drugs/info

POST /api/goodrx/drugs/info

Price: 20 credits

Get clinical information for a GoodRx drug by slug (or URL): the drug description, generic name, drug class, the conditions it is used for, prescription and legal status, administration route, official FDA label link, clinical warnings and the list of frequently asked questions with answers.

How to use it

Get clinical reference information for a prescription drug on GoodRx by slug (e.g. 'atorvastatin'). Returns the drug name, description, generic_name, drug_class, used_for (conditions it treats), prescription_status, legal_status, administration_route, label_url (FDA label), warning (clinical warnings) and faqs (question/answer pairs covering usage, side effects, interactions and dosing).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• drug string required — Drug slug or a GoodRx drug URL (examples: "atorvastatin", "https://www.goodrx.com/lipitor"; minLength: 1)

Response

• @type string (default: "GoodrxDrugInfo")
• slug string nullable
• name string nullable
• description string nullable
• generic_name string nullable
• drug_class string nullable
• image string nullable
• prescription_status string nullable
• legal_status string nullable
• administration_route string nullable
• label_url string nullable
• warning string nullable
• used_for array (default: [])
• faqs array (default: [])
  • @type string (default: "GoodrxDrugFaq")
  • question string nullable
  • answer string nullable

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 — Drug not found (well-formed but nonexistent drug slug) 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.