/viator/attractions

POST /api/viator/attractions

Price: 10 credits

Get a Viator attraction (point of interest) by its id (e.g. d511-a701) or attraction URL: name, description, address, star rating with review count, admission-free flag, themed info sections (know-before-you-go, ways to explore, how to get there, when to visit) and the tours & activities available at the attraction.

How to use it

Fetch one Viator attraction / point of interest by id (e.g. d511-a701 for the Colosseum) or attraction URL. Returns id, url, attraction_id, destination_id, name, destination, description, address, is_admission_free, rating + review_count, image, product_count (total tours at the attraction), best_seller_product_code, sections (heading + text: know-before-you-go / ways to explore / how to get there / when to visit) and products (related tours & activities with id, url, title, description, rating/rating_exact/review_count, price + currency, category, location, duration_minutes, languages, is_private_tour, is_new, has_free_cancellation, badges, latitude/longitude, image and max_travelers).

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "ViatorAttraction")
• id string required
• url string required
• attraction_id integer required
• destination_id integer required
• name string required
• destination string nullable
• description string nullable
• address string nullable
• is_admission_free boolean nullable
• rating number nullable
• review_count integer nullable
• image string nullable
• product_count integer nullable
• best_seller_product_code string nullable
• sections array (default: [])
  • @type string (default: "ViatorAttractionSection")
  • heading string required
  • text string nullable
• products array (default: [])
  • @type string (default: "ViatorAttractionProduct")
  • id string required
  • url string required
  • description string nullable
  • rating number nullable
  • rating_exact number nullable
  • review_count integer nullable
  • price number nullable
  • currency string nullable
  • category string nullable
  • location string nullable
  • duration_minutes integer nullable
  • languages array (default: [])
  • is_private_tour boolean nullable
  • is_new boolean nullable
  • has_free_cancellation boolean nullable
  • badges array (default: [])
  • latitude number nullable
  • longitude number nullable
  • image string nullable
  • max_travelers 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 — Attraction not found (well-formed id with no Viator attraction) 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.