/coolblue/products/search

POST /api/coolblue/products/search

Price: 10 credits

Search Coolblue products by keyword. Returns product cards with id, name, image, current price, list price (when discounted), rating and review count, plus the canonical product URL.

How to use it

Keyword search across the Coolblue catalog (NL). Each result has id (numeric Coolblue product id), alias (URL slug), name, url, image, price (current selling price in EUR), list_price (original price before discount, when present), currency, rating (1-5 scale — coarser than the 0-10 native Coolblue rating; fetch the product via coolblue/products for the precise value), and review_count. Coolblue is a first-party retailer (no third-party sellers / multi-offer pricing). For broad / popular intents some queries return minimal records (id, alias, url only); call coolblue/products with each id to retrieve full details. For exhaustive listings within a category use coolblue/categories/products.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "usb kabel", "iphone 15", "monitor 27 inch"; minLength: 1)
• count integer required — Max number of results to return (min: 1; max: 24)

Response

• @type string (default: "CoolblueSearchProduct")
• id string required
• alias string nullable
• name string nullable
• url string nullable
• image string nullable
• price number nullable
• list_price number nullable
• currency string nullable
• rating number nullable
• review_count integer 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 — The entity was not found, or a precondition failed 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.