# /kaufland/products/search

`POST /api/kaufland/products/search`

Price: 20 credits

Search Kaufland.de products by keyword. Returns product cards with title, images, price, list price, discount, base price, condition, seller, shipping cost, rating, review count, EAN, category, voucher and deal badges. Supports sorting and category, price, rating, delivery and attribute-facet filters. Roughly 340-790 products are reachable per query.

## How to use it

Keyword search across the Kaufland.de marketplace. Each result has id, title, url, image, images, price, list_price, discount_percent, discount_amount, currency, base_price with base_price_unit, condition (new / used_* / refurbished_* / download), rating, review_count, seller_id, seller_name, seller_company, shipping_cost, free_shipping, sold_by_kaufland, is_sold_out, is_bestseller, is_top_price, is_sponsored, badges, ean, offer_id, category_id, category_name, manufacturer, seller voucher (voucher_title, voucher_discount_percent or voucher_discount_amount in EUR, voucher_available_count), volume discount, and energy-label / product-information-sheet / tyre-label links where the category has them. Refine with sorting, category, min_price/max_price, rating, delivery, deals_only and numeric attribute-facet filters. Roughly 340-790 products are reachable per keyword, so a larger count returns everything there is. A keyword with no matches returns an empty list.

## 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: "playstation 5", "kaffeevollautomat"; minLength: 1)
- `count` (integer, required) — Max number of results to return (min: 1)
- `sorting` (string) — Result ordering to apply to the search (default: "natural"; one of: "natural", "price-asc", "price-desc", "newest-arrivals", "customer-reviews", "bestsellers")
- `category` (string, nullable) — Restrict the search to one category: a category id or a category URL containing it (examples: "46051", "https://www.kaufland.de/c/laptops/~46051/")
- `min_price` (number, nullable) — Minimum price filter in EUR (min: 0)
- `max_price` (number, nullable) — Maximum price filter in EUR (min: 0)
- `rating` (string, nullable) — Minimum average star rating filter (one of: "1", "2", "3", "4")
- `delivery` (string, nullable) — Delivery benefit filter (one of: "free_delivery", "3d")
- `deals_only` (boolean) — Only return products that are currently on deal (default: false)
- `filters` (object, nullable) — Attribute facet filters keyed by the NUMERIC facet id, e.g. {'351': '1883'} for a colour, {'421': '16000000000-32000000000'} for a numeric range, or {'2501': 't'} for a boolean feature. The available facet ids and values depend on the result category. A non-numeric key is rejected with 422. A numeric key is NOT validated: an id that does not exist for this query is ignored upstream and you get the unfiltered set back with a 200, not an error. A value the facet cannot parse (a non-numeric range, say) makes the source refuse the whole request and the call fails.
  - `*` (string)

## Response

### 200 — Successful Response

- `@type` (string) (default: "KauflandListingProduct")
- `id` (string, required)
- `url` (string, nullable)
- `image` (string, nullable)
- `images` (array) (default: [])
- `price` (number, nullable)
- `list_price` (number, nullable)
- `discount_percent` (number, nullable)
- `discount_amount` (number, nullable)
- `currency` (string, nullable)
- `base_price` (number, nullable)
- `base_price_unit` (string, nullable)
- `condition` (string, nullable)
- `rating` (number, nullable)
- `review_count` (integer, nullable)
- `seller_id` (string, nullable)
- `seller_name` (string, nullable)
- `seller_company` (string, nullable)
- `sold_by_kaufland` (boolean) (default: false)
- `shipping_cost` (number, nullable)
- `free_shipping` (boolean) (default: false)
- `is_sold_out` (boolean) (default: false)
- `is_best_offer` (boolean) (default: false)
- `is_bestseller` (boolean) (default: false)
- `is_top_price` (boolean) (default: false)
- `is_sponsored` (boolean) (default: false)
- `badges` (array) (default: [])
- `ean` (string, nullable)
- `offer_id` (string, nullable)
- `category_id` (string, nullable)
- `category_name` (string, nullable)
- `manufacturer` (string, nullable)
- `energy_class` (string, nullable)
- `energy_label_url` (string, nullable)
- `information_sheet_url` (string, nullable)
- `packaging` (string, nullable)
- `tyre_fuel_efficiency` (string, nullable)
- `tyre_label_url` (string, nullable)
- `voucher_title` (string, nullable)
- `voucher_discount_percent` (number, nullable)
- `voucher_discount_amount` (number, nullable)
- `voucher_available_count` (integer, nullable)
- `volume_discount_percent` (number, nullable)
- `volume_discount_min_quantity` (integer, 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

The entity was not found, or a precondition failed

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.