UK pharmacy and beauty catalog monitoring
Use Boots endpoints to turn uk pharmacy and beauty catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Boots UK — the country's largest pharmacy, health, and beauty retailer — into structured JSON: keyword and category search with dynamic facets, price and stock filtering, and search-box suggestions, all with one API key.
Search Boots UK's product catalog with live facets and price/stock filters, and get search-box suggestions, as structured JSON.
Endpoint families
2
Documented params
12
Examples
0
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
3
Schema refs
2
{
"platform": "Boots",
"endpoint": "boots-search",
"method": "GET",
"path": "/boots/search",
"auth": "apiKey"
}Use cases
Search Boots UK's product catalog with live facets and price/stock filters, and get search-box suggestions, as structured JSON.
Use Boots endpoints to turn uk pharmacy and beauty catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Use Boots endpoints to turn price and stock tracking into repeatable API requests with documented inputs and JSON responses.
Use Boots endpoints to turn search-term research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Boots endpoint catalog — 2 endpoints, 12 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Boots endpoints, grouped into 2 request families — Search and Suggest.
12 request parameters are documented across those Boots endpoints, 3 of them required — the full input contract is public before you write any integration code.
2 of the 2 Boots endpoints carry a documented response schema, so the JSON shape is known before you write any parsing code.
Boots endpoints document their error responses (400, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Boots endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/boots/search
/boots/suggest
Endpoint catalog
/boots/searchReturns one page of Boots UK's public product catalog, including product cards and live facets. Supply `q`, one or more hierarchical `category` keys, or both. Use repeatable `filter=facet_key:option_key` values from that response's dynamic facets, plus the dedicated price and stock controls. `sort` accepts `relevance`, `price_low_to_high`, `price_high_to_low`, `top_rated`, `best_seller`, or `newest`.
MCP tool boots_search
/boots/suggestReturns Boots UK's own public typeahead phrases for a partial product query. The suggestions are search terms only; pass one to boots-search's q parameter for product cards and live facets.
MCP tool boots_suggest
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Boots
Crawlora's Boots endpoints return normalized public Boots.com storefront data as JSON with one API key — no Boots account required.
Send a q keyword, one or more hierarchical category keys (from a prior response's category facet), or both to /boots/search. Add price_min, price_max, in_stock, page, page_size, and sort to narrow further, and repeat filter=facet_key:option_key for any other returned facet.
Each /boots/search response returns current facet metadata (brand, review score, colour, and more) alongside product cards — every non-special option is directly usable with filter, and category options keep their nested hierarchy in children.
Pass a partial product phrase to /boots/suggest for Boots' own public typeahead phrases, then feed a returned phrase back into /boots/search's q parameter.
FAQ
Call /boots/search with a q keyword, one or more category keys, or both — the response includes product cards, live facet metadata, and the upstream total, all with one API key.
Every returned facet (brand, colour, review score, and more) is usable with a repeated filter=facet_key:option_key parameter; category, price_min/price_max, and in_stock have their own dedicated parameters instead.
Current and regular price, per-unit price when supplied, stock and delivery/promotion messaging, Advantage Card points, basket eligibility, and whether colour or size variants exist.
No. Both endpoints read Boots' own public storefront and typeahead and require only your Crawlora API key.