Browse a CVS OTC category page API

Endpoint facts

Method

GET

API path

/cvs/category

Auth

apiKey

Credits

3 credits/request

Platform

CVS

Response schema

#/definitions/cvs.categoryResponseDoc

Overview

Returns one page of a CVS.com OTC (over-the-counter) retail category, subcategory, or brand page's product grid: normalized products with title, brand, image, current/original price, and sponsored/featured/new-product flags; the total result count; and the facets (brand, color, size, price range, and other category-specific attributes, each with its selectable values and result counts) available to filter the page further. Covers the non-prescription retail catalog only. path is the segment of a page URL after "/shop/", e.g. "beauty" (top-level category), "health-medicine/allergy-sinus" (subcategory), or "brand-shop/s/safe-home" (brand page); a full https://www.cvs.com/shop/... URL or a "/shop/..." path is also accepted. Any of these can also carry an optional facet-filter suffix in the site's own URL shape, e.g. "beauty/makeup/eyes/q/CoverGirl/Black/brpc" to filter to brand CoverGirl and color Black -- see the response's facets field for which values/type codes a given category supports; filter values are case-sensitive exactly as the site renders them. page is a 1-indexed page number (default 1). sort is an optional result order matching the site's own Sort By control. CVS.com is only available from US/US-territory egress; a request from an unsupported region returns an upstream error rather than an empty result. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- `list_price`/`sale_price`/`currency` come from the page's own pricing data; a product with no price omits these fields. - `is_sponsored`, `is_featured`, and `is_new_product` reflect the merchandising flags the category page itself carries. - `facets` lists every filter the current category/filter state exposes: `key` is the upstream facet field name (e.g. `brand`, `e_color`, `d_priceBucket`), `label` is its display name (e.g. `Brand`, `Color`, `Price`), and `values` is a list of `{name, count}` — `count` is the number of results selecting that value would produce given whatever filters, if any, the request already applied. The set of facets and their values is category-specific and upstream-controlled; read it from a live response rather than assuming a fixed set. - CVS.com is only available from US/US-territory egress; a request from an unsupported region, or a page CVS blocks, returns a `503` upstream error rather than an empty or wrong result. - An unrecognized `path` (including a malformed filter suffix) or an unrecognized `sort` value returns a `400` invalid-parameter error before any upstream request is made. Example response: ```json {"code":200,"msg":"OK","data":{"total_count":8766,"page":1,"products":[{"id":"478253","title":"Crest Pro-Health Breath Mist, Clean Mint, 0.44 OZ, 2 PK","url":"https://www.cvs.com/shop/crest-pro-health-breath-mist-clean-mint-0-44-oz-2-pk-prodid-478253","brand":"Crest","image_url":"https://www.cvs.com/bizcontent/merchandising/productimages/high_res/72894700032.jpg","currency":"USD","list_price":4.99,"sale_price":4.99}],"facets":[{"key":"brand","label":"Brand","values":[{"name":"Crest","count":12},{"name":"one+other","count":3}]},{"key":"d_priceBucket","label":"Price","values":[{"name":"$0 - $5","count":9},{"name":"$5 - $10","count":6}]}]}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related