Skip to main content
The OTA_TourActivityAvailRS (Tour & Activity Availability Response) returns available excursion services and pricing, corresponding to the search parameters sent in OTA_TourActivityAvailRQ. A <Success/> element indicates the request was processed; otherwise errors are returned. Results may be aggregated as one price-from per service (MF002) or expanded per product/subservice (MF001).

Structure – Root Element

Key Attributes:
  • xmlns: http://www.opentravel.org/OTA/2003/05.
  • Version: 2016.b (OTA Tour Activity messaging pack).
  • TransactionIdentifier: Correlates the transaction across systems (optional).

Structure – Core Elements

TourActivityInfo

Container for one available service result.

BasicInfo

Service identification and labeling for the product/subservice.
  • 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 summary for the specific departure/slot.
  • Summary/@Start: Start datetime (ISO 8601).
  • Summary/@End: End datetime (ISO 8601).
  • Summary/@Duration: ISO 8601 duration (e.g., PT8H).

CategoryAndType

Classification of the service.
  • Category/@Code: Category (e.g., Excursion vs Ticket).
  • Type/@Code: Activity type code (implementation-defined).

Description

Short text describing the service.
  • ShortDescription

Location

Where the service operates; includes postal address, regions, and geo position.
  • Address: AddressLine, CityName, PostalCode, Country, StateProv.
  • Region: @RegionCode values such as Country, Destination, Region, Resort, TravelDestination.
  • Position: @Latitude, @Longitude.

Pricing

Price container. Returned format depends on MF mode:
  • MF002 (price-from per service)Summary/@MinCharge with CurrencyCode; PricingType = PerPerson.
  • MF001 (detailed per product/subservice)Summary/@Amount with CurrencyCode; PricingType = PerGroup.

PickupDropoff (MF001 results with transfer service)

Operational pickup/dropoff information and indicators.
  • @PickupInd: true for pickup records; false for dropoff.
  • @DateTime: Pickup/dropoff local datetime.
  • @LocationName, @Code, @MeetingLocation: Operational details (as provided).

Complete Examples

Notes & Constraints

  • MF modes: MF002 returns a single price-from (per person) per service; MF001 returns detailed products/subservices priced per group with operational details like pickups.
  • Pickup/dropoff in Ticket-only services: Not included when the service is a pure ticket (no transfer).
  • Region usage: When regions are provided, Country is required; other levels (Destination/Region/Resort/TravelDestination) are optional as applicable.