An OTA Tour Activity Search Response message listing tour/excursion services for the requested area. It may include high‑level product metadata (ID, schedule, category, description, location, policies) and, where provided by the contract, indicative pricing.
SearchRS returns catalog data for services in scope. Use AvailRS for date/option‑level availability & final pricing.
Purpose
This message is used to:
- Return the catalog of tour activities matching the requested location(s).
- Provide service identifiers used later in Avail and Book flows.
- Convey descriptions, categories, locations, and policies (cancellation, participant rules).
- Optionally include expected/indicative rates for reference.
Structure – Root Element
Key Attributes:
Version: OTA messaging pack version (e.g., 2016.b)
xmlns: http://www.opentravel.org/OTA/2003/05
Structure – Core Elements
TourActivityInfo
Repeating container of returned services.
BasicInfo
SpecifieS the service identifiers.
SupplierProductCode: Specifies which product(unit) of a stock is being described.
Name: Full name of the tour.
ShortName: Name of the product.
TourActivityID: MTS activity code.
SupplierServiceCode: Type of service.
Schedule
Availability window for the service.
CategoryAndType
Indicates the excursoin type and category. Later in the avail request, these can be used to filter out responses.
Description
Shows main NBC content of the product:
- Short and long descriptions of the activity.
Multimedia with images of the activity. For more details, see MultimediaDescription.
TextItems describes different facts of the activity.
See Complete Examples.
Location
Location of the activity. Consists of:
Address.
Region hierarchy.
Position (geo codes).
PickupDropoff
The response includes all the operation times, duration of the service and pickup times. The attribute PickupInd=“true” indicates if the location and date time corresponds to the pickup (true) or dropoff (false).
Policies
May include:
CancelPolicy: Cancellation policy of the tour, similar structure as hotel cancel policies.
Participant: Participant rules.
Pricing
Returns the cheapest possible price for the tour and it’s type.
Complete Examples
Best Practices
- Expect empty lists when no services match the request; this is not an error.
- Treat any
Pricing in SearchRS as reference only; fetch final pricing with AvailRS before quoting.
- Persist
TourActivityID and any supplier codes for efficient follow‑up calls.
- Honor participant limits and cancellation rules surfaced in
Policies when building UI constraints.