# /coolblue/categories/products

`POST /api/coolblue/categories/products`

Price: 10 credits

List products in a Coolblue category by numeric category id, URL slug, or full category URL. Top-level product categories return the full inventory; facet sub-pages (brand, spec filter, etc.) return the products highlighted on that page. Each entry: id, alias, canonical product url. Use the returned ids with coolblue/products to fetch full per-product details.

## How to use it

List products inside a Coolblue category. Accepts a numeric category id (e.g. 2037), a URL slug (e.g. consoles, laptops, mobiele-telefoons), a facet path (e.g. mobiele-telefoons/smartphones/apple/apple-iphone-15), or the full category URL. Top-level categories return the full inventory; deeper facet pages return the subset of products highlighted on that facet page. Returns lite product entries: id, alias (slug fragment of the product URL), and the canonical product url. Pair with coolblue/products for full details.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `category` (string, required) — Category numeric id, URL slug, or full category URL. Accepts top-level product categories (full inventory) as well as deeper facet paths like brand or spec sub-pages (e.g. 'mobiele-telefoons/smartphones/apple') which return the products highlighted on the corresponding facet page. (examples: "2037", "consoles", "/consoles", "https://www.coolblue.nl/laptops", "mobiele-telefoons/smartphones/apple/apple-iphone-15"; minLength: 1)
- `count` (integer, required) — Max number of results (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "CoolblueCategoryProduct")
- `id` (string, required)
- `alias` (string, nullable)
- `url` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

Category not found (unknown id, slug, or facet path that yields no products)

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.