/trivago/hotels

POST /api/trivago/hotels

Price: 1 credit

Get full Trivago hotel details by accommodation id. Returns name, accommodation type, chain, star classification, guest rating with review count and top scored aspects, coordinates, country, locality, check-in/check-out hours, construction year, free WiFi, highlights, main image, image count, page URL, destination hierarchy and room/unit details.

How to use it

Fetch a single Trivago hotel by accommodation id (numeric, ns/id, or an accommodation URL). Returns one item with id, name, accommodation_type, category, star_rating, is_superior, rating (guest score 0-10), review_count, aspects (categories the property scores well on), is_popular, has_free_wifi, construction_year, latitude, longitude, country, locality, locality_id, location_label, distance_label, check_in_hour, check_out_hour, image, image_count, alias, url, destination_hierarchy (geo levels from city up to continent) and units (capacity, bedroom/bathroom counts, size).

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")
• hotel string required — Trivago accommodation id, or an accommodation URL / nsid containing it (examples: "8551", "100/8551", "100-8551"; minLength: 1)

Response

• @type string (default: "TrivagoHotel")
• id integer required
• name string required
• accommodation_type string nullable
• category string nullable
• star_rating integer nullable
• is_superior boolean nullable
• rating number nullable
• review_count integer nullable
• aspects array (default: [])
• is_popular boolean nullable
• has_free_wifi boolean nullable
• construction_year integer nullable
• latitude number nullable
• longitude number nullable
• country string nullable
• locality string nullable
• locality_id integer nullable
• location_label string nullable
• distance_label string nullable
• check_in_hour integer nullable
• check_out_hour integer nullable
• image string nullable
• image_count integer nullable
• alias string nullable
• url string nullable
• destination_hierarchy array (default: [])
  • @type string (default: "TrivagoGeoRef")
  • id integer required
  • name string required
  • type string nullable
• units array (default: [])
  • @type string (default: "TrivagoUnit")
  • adult_capacity integer nullable
  • children_capacity integer nullable
  • bedroom_count integer nullable
  • bathroom_count integer nullable
  • size_value number nullable
  • size_unit string 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 — Hotel not found (well-formed but nonexistent accommodation 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.