# /idealo/products/price-history

`POST /api/idealo/products/price-history`

Price: 1 credit

Get the daily price history Idealo has recorded for one product on a chosen national Idealo site over the last three months, six months or year: one point per recorded day with its date and lowest price, plus the period's average, lowest and highest price, how many days each extreme held, and how many days of the period carry a recorded price at all.

## How to use it

Answers 'is this a good time to buy' and 'has this price moved': compare `points[-1].price` against `lowest_price` and `avg_price` for the period. Every price is the cheapest offer of that day excluding shipping, on the same basis as `idealo/products.price`, so the series is comparable with it but not with `idealo/products/offers.total_price`. `days_with_data` is what tells you the series is thin: a product listed only recently returns far fewer points than the period has days, and reading a trend off those is misleading. Each national site prices independently, so a history for `country=fr` says nothing about the German price. Widen `period` to 1Y for seasonal products rather than inferring a trend from 3M.

## 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: "204743522", "https://www.idealo.de/preisvergleich/OffersOfProduct/204374464_-portasplit-3-5-kw-midea.html"; minLength: 1)
- `country` (string) — National Idealo site to read the price history from. Each site prices the product independently, so the series differ (default: "de"; one of: "de", "at", "gb", "fr", "it", "es")
- `period` (string) — How far back the series reaches: three months, six months or one year (default: "3M"; one of: "3M", "6M", "1Y")

## Response

### 200 — Successful Response

- `@type` (string) (default: "IdealoPriceHistory")
- `id` (string, required)
- `site_id` (string, required)
- `country` (string, required)
- `currency` (string, required)
- `period` (string, required)
- `start_date` (string, nullable)
- `avg_price` (number, nullable)
- `lowest_price` (number, nullable)
- `lowest_price_days` (integer, nullable)
- `highest_price` (number, nullable)
- `highest_price_days` (integer, nullable)
- `days_with_data` (integer, nullable) — How many days of the requested period Idealo actually recorded a price for
- `points` (array) (default: [])
  - `@type` (string) (default: "IdealoPricePoint")
  - `date` (string, required)
  - `price` (number, 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

No such product on this national Idealo site, or no price has ever been recorded for it there

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.