# /kaufland/sellers

`POST /api/kaufland/sellers`

Price: 20 credits

Get a Kaufland.de seller (shop) by name or shop URL: seller id, name, shop URL, shop logo, the merchant's own website, the number of the seller's products this endpoint reached and a list of those products, each with the seller's own price, condition, shipping, rating, EAN, category, voucher and deal badges.

## How to use it

Fetch one Kaufland.de shop and its catalogue by shop name or shop URL; the name is case-insensitive and alias comes back as the lowercase canonical form. To find shops, take seller_name off any product card returned by products/search or categories/products. Every product here carries THIS seller's own offer — its price, condition and offer_id — while the same product id in products/search carries whichever seller currently holds the buy box, so the two legitimately disagree on price for the same product. product_count is how many products the shop feed actually served, not the far larger figure the shop page advertises, and it is present only when the whole feed was walked and omitted when count stopped the walk earlier. Up to a few hundred products are reachable per shop however large count is. A shop that exists but currently lists nothing returns an empty products list; only a shop name the source does not know is 412.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `seller` (string, required) — Kaufland.de seller (shop) name or a shop URL containing it (examples: "ANTCOOL", "https://www.kaufland.de/shops/ANTCOOL/"; minLength: 1)
- `count` (integer, required) — Max number of seller products to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "KauflandSeller")
- `id` (string, nullable)
- `name` (string, nullable)
- `alias` (string, nullable)
- `url` (string, nullable)
- `image` (string, nullable)
- `homepage_url` (string, nullable)
- `product_count` (integer, nullable)
- `products` (array) (default: [])
  - `@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

Seller not found (well-formed but nonexistent shop name)

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.