/goodrx/drugs/prices

POST /api/goodrx/drugs/prices

Price: 20 credits

Get pharmacy prices for a prescription drug in a US ZIP code: for each pharmacy the GoodRx coupon price, the retail price and the lowest available price, plus the drug form and dosage that was priced.

How to use it

Compare prescription drug prices across pharmacies in a specific US ZIP code. Provide the drug slug (e.g. 'atorvastatin') and a 5-digit ZIP. Optionally narrow by form, dosage and quantity. Returns a list of pharmacies, each with pharmacy_name, pharmacy_id, pharmacy_image, price (GoodRx coupon price), retail_price and lowest_price (plus whether the lowest price requires a paid subscription tier). This is GoodRx's core price-comparison data.

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/atorvastatin"; minLength: 1)
• location string required — US ZIP code to price the prescription in (examples: "10001", "90210"; minLength: 1)
• form string nullable — Drug form (e.g. tablet, capsule) (examples: "tablet")
• dosage string nullable — Drug dosage (e.g. 20mg) (examples: "20mg")
• quantity integer nullable — Number of units to price (examples: 30, 90; >: 0)
• count integer required — Max number of pharmacy prices to return (min: 1)

Response

• @type string (default: "GoodrxPharmacyPrice")
• pharmacy_id string nullable
• pharmacy_name string nullable
• pharmacy_image string nullable
• price number nullable
• retail_price number nullable
• lowest_price number nullable
• lowest_price_requires_subscription boolean (default: false)
• lowest_price_subscription 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 or location not found (well-formed but nonexistent drug slug, or no prices available) 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.