From 01610f7dcea1ecdbfdbbf9d938f429550267adc9 Mon Sep 17 00:00:00 2001 From: pstarritt-gyg Date: Thu, 13 Aug 2026 12:00:57 +0200 Subject: [PATCH] Document activity_type field on Tour schema The GET /tours response returns an activity_type field (passed through from the Search service), but it was never documented in the public Partner API spec. Partners integrating against /tours were seeing undocumented values such as privateTour and multiDayTrip. Add activity_type to the Tour schema as a descriptive string with the common values documented and an example. It is intentionally NOT modelled as an enum: the value set is not closed upstream, so an enum would falsely imply a fixed set and could break partner codegen when new values are introduced. Co-Authored-By: Claude Opus 4.8 (1M context) --- spec/components/schema/tour.yaml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/spec/components/schema/tour.yaml b/spec/components/schema/tour.yaml index 7f6a4b7..d3532cf 100644 --- a/spec/components/schema/tour.yaml +++ b/spec/components/schema/tour.yaml @@ -110,6 +110,26 @@ components: type: array items: $ref: "#/components/schemas/TourCategoryMinimal" + activity_type: + type: string + description: > + The main type of the activity. This is a descriptive classification, + not a fixed/closed set — new values may be introduced over time, so + integrations should tolerate unrecognised values. Common values include: + * `entryTicket`: entry ticket / admission. + * `hostedTicket`: ticket including a host or greeter. + * `ticket`: generic ticket. + * `guidedTour`: guided tour. + * `privateTour`: private tour. + * `multiDayTrip`: multi-day trip. + * `dayTrip`: day trip. + * `cityCard`: city card or pass. + * `waterActivity`: water-based activity. + * `workshopOrClass`: workshop or class. + * `hopOnHopOff`: hop-on hop-off. + * `bundle`: bundled product. + * `transfer`: transfer. + example: entryTicket health_advisory: $ref: "#/components/schemas/HealthAdvisory" health_requirement: