/idealo/products

POST /api/idealo/products

Price: 10 credits

Get an Idealo product by product id (or product URL) on a chosen national Idealo site: name, brand, category and top-level category, category id, the current lowest offer price and lowest price including shipping with their currency, delivery-time bucket, online availability, energy class, product page URL and images, plus the price per reference unit for products sold by volume or weight and the EU tyre label for tyres.

How to use it

Fetch one Idealo product by numeric product id or a product URL, optionally on a specific national Idealo site. Returns one item with name, brand, category/main_category (in that site's language), category_id, price and total_price (lowest offer, and lowest including shipping) with currency, delivery_status, is_available_online, is_main_product, energy_class, url, image/thumbnail, base_price (amount/unit/price/total_price for goods priced per litre or kilo) and tyre_label (EU tyre label classes, rolling noise in dB, ice and snow grip). Price and availability differ per site; a product not listed on the chosen site answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Idealo product id or a product URL containing it (examples: "204374464", "https://www.idealo.de/preisvergleich/OffersOfProduct/204374464_-portasplit-3-5-kw-midea.html"; minLength: 1)
• country string — National Idealo site to read the product from. The product itself is the same across sites, but its price, availability, currency, page URL and the language of the category names are per site, and a product listed in one country may be absent in another (default: "de"; one of: "de", "at", "gb", "fr", "it", "es")

Response

• @type string (default: "IdealoProduct")
• id string required
• site_id string required
• country string required
• currency string required
• name string nullable
• url string nullable
• brand string nullable
• category string nullable
• category_id string nullable
• main_category string nullable
• price number nullable
• total_price number nullable
• delivery_status string nullable
• is_available_online boolean nullable
• is_main_product boolean nullable — Mirrors upstream's undocumented `mainProduct` flag, passed through verbatim. Idealo documents no meaning for it and the page that would show what it corresponds to is not reachable, so it is exposed as-is rather than renamed to a guess.
• energy_class string nullable
• image string nullable
• thumbnail string nullable
• base_price object nullable — Price per reference quantity, for products sold by volume or weight (oils, detergents).
  • @type string (default: "IdealoProductBasePrice")
  • amount number nullable
  • unit string nullable
  • price number nullable
  • total_price number nullable
• tyre_label object nullable — The EU tyre label, present on tyre listings only.
  • @type string (default: "IdealoProductTyreLabel")
  • fuel_efficiency_class string nullable
  • wet_grip_class string nullable
  • rolling_noise_class string nullable
  • rolling_noise_db integer nullable
  • has_ice_grip boolean nullable
  • has_snow_grip 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 id that this national Idealo site does not list) 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.