/trivago/destinations

POST /api/trivago/destinations

Price: 1 credit

Get a Trivago destination by id. Returns the destination name, geo level, location label, the full destination hierarchy (from the destination up to the continent) and its geographic bounding box.

How to use it

Fetch a single Trivago destination by id (numeric, ns/id, or a search token). Returns one item with id, name, type (City, Subregion, Region, Country or Continent), location_label, destination_hierarchy (parent geo levels) and bounding_box (north-east / south-west corner coordinates).

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)

Response

• @type string (default: "TrivagoDestinationDetail")
• id integer required
• name string required
• type string nullable
• location_label string nullable
• destination_hierarchy array (default: [])
  • @type string (default: "TrivagoGeoRef")
  • id integer required
  • name string required
  • type string nullable
• bounding_box object nullable
  • @type string (default: "TrivagoBoundingBox")
  • north_east_latitude number nullable
  • north_east_longitude number nullable
  • south_west_latitude number nullable
  • south_west_longitude 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 (well-formed but nonexistent destination 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.