/getyourguide/activities

POST /api/getyourguide/activities

Price: 1 credit

Get full GetYourGuide activity (tour/experience) details by id or activity URL: title, abstract and full description, highlights, duration, price, inclusions and exclusions, what to bring, not allowed and good to know notes, key details, itinerary stops, meeting point with coordinates, rating and rating breakdown by topic, review count, languages, supplier, city, and photos.

How to use it

Fetch a single GetYourGuide activity by id (e.g. 193940 or t193940) or an activity URL. Returns one item with id, title, abstract, description, url, alias (slug), duration, cancellation_policy, languages, highlights, inclusions, exclusions, what_to_bring, not_allowed, good_to_know, key_details (title + description rows such as cancellation/duration/audio guide/accessibility), itinerary (stops with name and description), meeting_point (description, latitude, longitude), price (amount, formatted, unit), rating, review_count, rating_categories (per-topic ratings), supplier (id, name, url), city_id, and image + images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• activity string required — GetYourGuide activity id (e.g. 193940 or t193940) or an activity page URL containing it (examples: "193940", "https://www.getyourguide.com/paris-l16/paris-1-hour-seine-cruise-departing-from-the-eiffel-tower-t193940/"; minLength: 1)

Response

• @type string (default: "GetYourGuideActivity")
• id integer required
• abstract string nullable
• description string nullable
• url string required
• alias string nullable
• duration string nullable
• cancellation_policy string nullable
• languages array (default: [])
• highlights array (default: [])
• inclusions array (default: [])
• exclusions array (default: [])
• what_to_bring array (default: [])
• not_allowed array (default: [])
• good_to_know array (default: [])
• key_details array (default: [])
  • @type string (default: "GetYourGuideKeyDetail")
  • description string nullable
• itinerary array (default: [])
  • @type string (default: "GetYourGuideItineraryStop")
  • name string required
  • description string nullable
• meeting_point object nullable
  • @type string (default: "GetYourGuideMeetingPoint")
  • description string nullable
  • latitude number nullable
  • longitude number nullable
• price object nullable
  • @type string (default: "GetYourGuidePrice")
  • amount number nullable
  • formatted string nullable
  • unit string nullable
• rating number nullable
• review_count integer nullable
• rating_categories array (default: [])
  • @type string (default: "GetYourGuideRatingCategory")
  • name string required
  • rating number nullable
• supplier object nullable
  • @type string (default: "GetYourGuideSupplier")
  • id string nullable
  • name string nullable
  • url string nullable
• city_id integer nullable
• image string nullable
• images array (default: [])

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 — Activity not found (well-formed but nonexistent activity id, or page has no activity) 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.