/kaufland/products/buy-box

POST /api/kaufland/products/buy-box

Price: 1 credit

Get the buy-box (winning offer) for a Kaufland.de product by product id: price, UVP, reference price, discount, condition, availability, delivery details and the winning seller.

How to use it

Buy-box (currently winning offer) for a Kaufland.de product (numeric id or product URL). Returns one item with unit_id, price, uvp, reference_price, discount_off_uvp, currency, condition, amount_left, is_in_stock, delivery_time, delivery_days_max, shipping_rate, fulfillment_type and seller (id/name/shop_url/return_period/is_direct_seller).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Kaufland.de product id or a product URL containing it (examples: "483046862", "https://www.kaufland.de/product/483046862/"; minLength: 1)
• storefront string (default: "de"; one of: "de", "at", "cz", "sk", "it", "fr")

Response

• @type string (default: "KauflandBuyBox")
• unit_id string nullable
• price number nullable
• uvp number nullable
• reference_price number nullable
• discount_off_uvp number nullable
• currency string nullable
• condition string nullable
• amount_left integer nullable
• is_in_stock boolean nullable
• delivery_time string nullable
• delivery_days_max integer nullable
• shipping_rate number nullable
• fulfillment_type string nullable
• seller object nullable
  • @type string (default: "KauflandBuyBoxSeller")
  • id integer nullable
  • name string nullable
  • shop_url string nullable
  • return_period string nullable
  • is_direct_seller boolean 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 — Product not found (well-formed but nonexistent id, or product has no current offer) 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.