Walgreens prices, UPC/GTIN and full OTC labels from one API
Walgreens API returns live Walgreens data as clean JSON for walgreens The primary endpoint, search, returns matching records including product id, sku id, title, display title and brand.
4 active endpoints, on 1, 2 and 3 credit tiers.
- POST/walgreens/v1/search
- POST/walgreens/v1/category/products
- POST/walgreens/v1/product/detail
- POST/walgreens/v1/product/batch
What Walgreens endpoints does ReefAPI ship?
4 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Walgreens API
4 of 4 endpoints, ready to run
Search walgreens.com for up to 72 products with price, promotion, UPC, GTIN-14 and availability. This surface publishes one page; the response reports the source's own total beside the rows.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Walgreens API works
Walgreens is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 438 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Keyword to a priced, labelled, GTIN-keyed product file
Search gives ids, prices and the aisle id on every row. One batch call turns those ids into full records with the exact rating and the OTC label, and the aisle id opens the rest of the shelf.
Read product_id, USD price, UPC, GTIN-14, in_stock and category_ids.tier3 from each row. Measured: 24 of 24 rows carried all of them.
ids from step 1>
One request returns 15 full records with the exact rating, brand, ingredients and warnings. Measured: 15 of 15 ids resolved, and price and GTIN matched the search rows 15 times out of 15.
Open the whole aisle behind those rows. The response carries total, last_page, page_cap and has_more, so paging stops where Walgreens stops.
A product file keyed on GTIN-14 with the shelf price, the sale price kept separate, multi-buy deals in their published form, per-unit price with its denominator, availability, the exact review average and the full OTC label — three requests for 15 products plus a full aisle.
curl -X POST https://api.reefapi.com/walgreens/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"ibuprofen","max_results":24}'{
"ok": true,
"data": { … },
"meta": {
"api": "walgreens",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}Measured US coverage, field fill and where paging stops
Measured on 3 October 2026 across four aisles (pain relief, shampoo, diapers, toothpaste), three keywords and 96 products, counted per aisle rather than pooled. Lines that go against us are here too.
walgreens.com, United States, USD
One page of up to 72 products; the source ignores a page parameter on this surface, and the response says so
Up to 100 products per page and 15 pages — 1,500 per aisle. Page 16 is refused by Walgreens at every page size
Up to 50 product ids in one request; asked 15, 25 and 50, got 15, 25 and 50 records
24 of 24 rows carried product_id, title, URL, brand, size, UPC, GTIN-14, price, unit price, availability and the aisle ids
124 of 124 rows carried the same core fields; price was absent on 1 of 124, ingredients only on medicine aisles (27 of 124)
15 of 15 carried price, brand, UPC, GTIN-14, description, warnings, ingredients, shipping weight and the aisle path; the exact rating on 14 of 15
Search row price matched the full record on 15 of 15 products in the same minute; GTIN matched on 15 of 15
Listing rows publish a half-star bucket — equal to the exact average on only 20 of 96. The exact average comes from the full record
Coupon label and terms on 16 of 124 aisle rows, 30 of 72 toothpaste rows; a real sale price with the source's flag set to false on 28 of 96
Individual review texts, per-store price, per-store stock, a stock count and price history are absent, not guessed
Walgreens does not support them on this surface, so the API does not offer them
What people build with Walgreens
The jobs this data is most often used for.
endpoints
credits per call
Pricing teams use Walgreens to search walgreens.com by keyword and get up to 72 products with price, promotion, unit price,….
Marketplace operators use Walgreens to list the products of one or more Walgreens categories (tier-3 aisle ids, the same ids every p….
Catalog enrichment teams use Walgreens to get the full Walgreens product record by product id or product URL.
Retail analysts use Walgreens to get the same full product record as `product/detail` for up to 50 product ids in ONE upstream call.
What Walgreens data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 438 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/walgreens/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"ibuprofen","max_results":24}'import requests
r = requests.post(
"https://api.reefapi.com/walgreens/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "ibuprofen",
"max_results": 24
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Walgreens.
Get a free key →What is the Walgreens API?▾
Walgreens API is a ReefAPI endpoint group for walgreens It returns live JSON through POST requests under /walgreens/v1.
Is the Walgreens API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Walgreens calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Walgreens login or account?▾
No login to Walgreens is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Walgreens data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Walgreens API use?▾
Walgreens actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Walgreens from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call walgreens actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Walgreens API a Walgreens scraper?▾
It is the managed alternative to a DIY Walgreens scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same walgreens back as clean JSON.
Why does my Walgreens scraper keep getting blocked?▾
Most Walgreens scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.
191 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Walgreens, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 437 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-03.