/viator/products

POST /api/viator/products

Price: 20 credits

Get a Viator tour or activity ('product') by its id (e.g. d511-169766P7) or product URL: title, description, highlights, photos, star rating with review breakdown, price, duration, languages, inclusions/exclusions, cancellation policy, itinerary stops, departure locations, supplier and recent reviews.

How to use it

Fetch one Viator tour/activity by id (e.g. d511-169766P7) or product URL. Returns title, description, highlights, product_type, destination+destination_id, location_label, rating/rating_exact/review_count, rating_breakdown (per-star counts), price+currency, duration_minutes, supplier_id/supplier_name/is_supplier_business, primary_language+languages, inclusions, exclusions, additional_info, cancellation_policy + has_free_cancellation + free_cancellation_from_days, itinerary_type + itinerary (stops with name/duration_minutes/lat/lon/admission_included/attraction_id), departure_locations, image+images, tour_grades, is_private_tour, is_likely_to_sell_out and reviews (author/rating/title/text/created_at/helpful_count).

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "ViatorProduct")
• id string required
• url string required
• description string nullable
• highlights array (default: [])
• product_type string nullable
• destination string nullable
• destination_id integer nullable
• location_label string nullable
• rating number nullable
• rating_exact number nullable
• review_count integer nullable
• rating_breakdown array (default: [])
  • @type string (default: "ViatorRatingBucket")
  • rating integer required
  • review_count integer nullable
• price number nullable
• currency string nullable
• duration_minutes integer nullable
• supplier_id string nullable
• supplier_name string nullable
• is_supplier_business boolean nullable
• time_zone string nullable
• primary_language string nullable
• languages array (default: [])
• inclusions array (default: [])
• exclusions array (default: [])
• additional_info array (default: [])
• cancellation_policy string nullable
• has_free_cancellation boolean nullable
• free_cancellation_from_days integer nullable
• itinerary_type string nullable
• itinerary array (default: [])
  • @type string (default: "ViatorItineraryStop")
  • name string nullable
  • duration_minutes integer nullable
  • latitude number nullable
  • longitude number nullable
  • admission_included boolean nullable
  • attraction_id integer nullable
• departure_locations array (default: [])
  • @type string (default: "ViatorLocation")
  • description string nullable
  • instructions string nullable
  • type string nullable
• image string nullable
• images array (default: [])
• tour_grades array (default: [])
• is_private_tour boolean nullable
• is_likely_to_sell_out boolean nullable
• reviews array (default: [])
  • @type string (default: "ViatorReview")
  • id integer required
  • author string nullable
  • rating integer nullable
  • text string nullable
  • created_at string nullable
  • helpful_count integer 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 — Product not found (well-formed id with no Viator product) 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.