/viator/destinations

POST /api/viator/destinations

Price: 10 credits

Get a Viator destination by its id (e.g. 511 for Rome) or destination URL: name, description, country, parent destination, the full geo hierarchy (ancestors) and the number of tours & activities available there.

How to use it

Fetch one Viator destination by numeric id (e.g. 511 for Rome) or destination URL. Returns id, url, name, alias (URL slug), description, country, parent_destination (immediate parent region/country name) + parent_id, city_name (set only for city-level destinations), activity_count (number of tours & activities) and ancestors (the geo hierarchy from country down to the destination, each with id/name/url).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• destination string required — Viator destination id (e.g. 511 for Rome) or a destination URL containing it (examples: "511", "d511", "https://www.viator.com/Rome/d511-ttd"; minLength: 1)

Response

• @type string (default: "ViatorDestination")
• id integer required
• url string required
• name string required
• alias string nullable
• description string nullable
• country string nullable
• parent_destination string nullable
• parent_id integer nullable
• city_name string nullable
• activity_count integer nullable
• ancestors array (default: [])
  • @type string (default: "ViatorDestinationAncestor")
  • id integer required
  • name string required
  • url 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 — Destination not found (well-formed id with no Viator destination) 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.