/trivago/destinations/forecast

POST /api/trivago/destinations/forecast

Price: 1 credit

Get a Trivago monthly hotel price forecast for a destination. Returns, per upcoming month, the affordability band and price statistics (minimum, maximum, average, median, 10th and 90th percentile) for a night's stay — the 'best time to book' price trend.

How to use it

Fetch the monthly price forecast for a Trivago destination. Returns one item per month with year_month (YYYY-MM), affordability (INEXPENSIVE, MODERATELY_EXPENSIVE, EXPENSIVE, VERY_EXPENSIVE), minimum, maximum, average, median, tenth_percentile and ninetieth_percentile nightly prices in the requested currency.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• locale string — Market language-region tag that localizes names, availability and content (default: "en-US"; examples: "en-US", "de-DE", "fr-FR", "es-ES", "ja-JP")
• currency string — ISO 4217 currency code prices are returned in (default: "USD"; examples: "USD", "EUR", "GBP", "JPY")
• destination string required — Trivago destination id, or an nsid / search token containing it (examples: "14667", "200/14667", "200-14667"; minLength: 1)
• months integer required — Number of upcoming months to forecast, starting from the current month (min: 1; max: 24)

Response

• @type string (default: "TrivagoMonthlyForecast")
• year_month string required
• affordability string nullable
• minimum number nullable
• maximum number nullable
• average number nullable
• median number nullable
• tenth_percentile number nullable
• ninetieth_percentile number 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 — Destination not found or no forecast available for the given id 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.