OTA Model Viewer | Format | Pilotfish Technology

Index of Message Types
AccommodationService	Detailed description of accommodations and services.
FareRuleType	A price and rule combination.
OTA_AirAvailRQ	The Availability Request message requests Flight Availability for a city pair on a specific date for a specific number and type of passengers. Optional request information can include:Time / Time Window, Connecting cities, Client Preferences (airlines, cabin, flight types etc.) The request can be narrowed to request availability for a specific airline, specific flight, or specific booking class on a specific flight. The availability request message contains similar information to a standard Airline CRS or GDS availability request message.
OTA_AirAvailRS	The Availability Response message contains Flight Availability for a city pair on a specific date. A set of OriginDestinationOptions is returned, each of which contains one or more (connecting) flights that serve the city pair. For each flight the following information is returned: Origin and destination airports, Departure and arrival date/times, Booking Class availability, Equipment, Meal Information and Codeshare information. This message contains similar information to a standard airline CRS or GDS availability response message.
OTA_AirBaggageRQ	OpenTravel Air Baggage Request.
OTA_AirBaggageRS	OpenTravel Air Baggage Response.
OTA_AirBookModifyRQ	The AirBook Modify Request message requests the system to modify an existing booking for one or more identified passengers. The message may be used for any kind of modification to a booking file, i.e. a modification to existing flight segments and special service information the addition of new elements, a name change or a booking file split. Analogous to the TTY process, existing data is submitted as well as the modified data. Attribute 'Operation' indicates the way elements have to be changed. Flight segments as well as seats- and special service requests will indicate a modification using the appropriate Status attribute.
OTA_AirBookRQ	The Book Request message requests the system to book a specific itinerary for one or more identified passengers. The message contains optional pricing information, allowing the booking class availability and pricing to be rechecked as part of the booking process. Optional request information can include: Seat and Meal Requests, SSR, OSI, and Remarks.
OTA_AirBookRS	The Book Response message contains the itinerary, passenger and pricing information sent in the request, along with a Booking reference number (PNR Locator) and ticketing information if the booking was successful. This message contains similar information to a standard airline CRS or GDS Display PNR message.
OTA_AirCheckInRQ	This message provides an air travel check-in product specifically for the self-service channels (kiosks, web and mobile). The message will allow a customer, multiple customers or groups traveling together and employees to check-in for eligible flights.
OTA_AirCheckInRS	This message provides check-in response information.
OTA_AirDemandTicketRQ	Provides the capability of requesting that a company responsible for ticket fulfillment, such as a GDS, issue an electronic ticket and/or automated miscellaneous charge order (MCO). The ticket fulfillment company would then issue the ticket using the current EDIFACT message.
OTA_AirDemandTicketRS	Provides the capability to respond to a demand ticket request, returning minimal information about the ticket that was issued.
OTA_AirDetailsRQ	The AirDetails Request message is used to request additional flight details for each leg of a flight (e.g. journey time, meal service). The request includes necessary information to identify a specific flight: Airline; Flight Number; Departure Airport; Arrival Airport; and Departure Date.
OTA_AirDetailsRS	The AirDetails Response message provides additional flight details for each leg of a flight (e.g. journey time, meal service). Types of information in the response include: Marketing Airline; Board and Off points for each flight leg; Operating Airline; Equipment; and Meal service for each cabin type.
OTA_AirDisplayQueueRS	Returns booking files on queue and reason for queuing.
OTA_AirFareDisplayRQ	The air fare display request enables display of fares between a given city pair.
OTA_AirFareDisplayRS	Response message contains the various fares for a given origin and destination, including some general fare conditions (e.g., minimum/maximum stay).
OTA_AirFlifoRQ	Retrieve real-time flight departure, arrival and gate information for a particular flight, including actual as well as scheduled departure and arrival times.
OTA_AirFlifoRS	Details of flight departure, arrival and gate information for a particular flight, including actual as well as scheduled departure and arrival times.
OTA_AirGetOfferRQ	The Get Offer request message provides trip and passenger characteristics to be used by an offer processing system to target relevant offers. Request criteria may be specified for the entire trip or by individual traveler and/or arranger and include any combination of the following: » Confirmed booking —including air itinerary, traveler/arranger, purchased offers, payment, pricing and ticketing information » Pre-booking —including origin/destination, itinerary, traveler/arranger preferences and specific flight information » Baggage —including item type, quantity, description, origin/destination, marketing/operating carriers and traveler/itinerary association » Seat information —including marketing classification, requested quantity and traveler/itinerary association » Offers to include and/or exclude » Offers that have already been presented and/or purchased Additional supported business functionality includes: » Offer family encoding by airline suppliers and/or ATPCO » Detailed point of sale information » Pricing structure flexibility, including display/ pricing currency(s), ticketing country/ city, and loyalty program redemption support » Offer stages that specify the stage in the journey at which the ancillary offer request is being made or the offer was purchased, e.g. shopping and check-in » Travel insurance product offers included with ancillary offers
OTA_AirGetOfferRS	The Get Offer response message returns relevant offers that meet the search criteria. Returned information includes: » Pricing structure details—including exchange rates, currency overrides and accepted payment currency that apply to all offers unless override information is provided elsewhere in the message » Priced offers—Priced offer information, including offer name and description, maximum and minimum offer quantity(s), service family, pricing details including redemption mile pricing, booking instructions, restrictions, penalties, multimedia, commissions and currency overrides Developer Notes: » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_AirLowFareSearchRQ	The Low Fare Search Request message requests priced itinerary options for flights between specific city pairs on specific dates for specific numbers and types of passengers. Optional request information can include: Time / Time Window; Connecting cities; and Client Preferences (airlines, cabin, flight types etc.) The Low Fare Search request contains similar information to a Low Fare Search entry on an airline CRS or GDS.
OTA_AirLowFareSearchRS	The Low Fare Search Response message contains a number of Priced Itinerary options. Each includes: A set of available flights matching the client's request; Pricing information including taxes and full fare breakdown for each passenger type; Ticketing information; and Fare Basis Codes and the information necessary to make a rules entry. This message contains similar information to a standard airline CRS or GDS Low Fare Search Response message.
OTA_AirPriceRQ	The Price Request message requests pricing information for specific flights on specific dates for a specific number and type of passengers. Optional information in the message allows fare restriction preferences and negotiated fare contract codes to be included in the message. The pricing request contains the information necessary to perform an availability / sell from availability / price series of entries on an airline CRS or GDS.
OTA_AirPriceRS	The Pricing Response message contains a Priced Itinerary. This includes: The set of flights sent in the Pricing request message; Pricing information including taxes and full fare breakdown for each passenger type; Ticketing information; and Fare Basis Codes and the information necessary to make a Fare Rules entry. This message contains similar information to a standard airline CRS or GDS itinerary pricing response message.
OTA_AirRulesRQ	The Rules Request message requests text rules for a specific fare class code for an airline and city pair on a specific date. Optional information negotiated fare contract codes to be included in the message. The rules request contains similar to a Fare Rules entry on an airline CRS or GDS.
OTA_AirRulesRS	The Rules Response message contains a set of text (human readable) rule information paragraphs. Each paragraph is identified by a rule code. This message contains similar information to a standard airline CRS or GDS Fare Rules Response message.
OTA_AirScheduleRQ	The Schedule Request message requests Flight Schedules for a city pair. Optional request information can include: Time / Time Window; Connecting cities; and Client Preferences (airlines, cabin, flight types etc.) The request can be narrowed to request schedules for a specific airline or specific flight.
OTA_AirScheduleRS	The Schedule Response message contains Flight Schedules for a city pair. A set of OriginDestinationOptions is returned, each of which contains one or more (connecting) flights that serve the city pair. For each flight the following information is returned: Origin and destination airports; Departure and arrival times; Days of Operation; Effective Date and End Date; Equipment; Meal Information; and Codeshare information. This message contains similar information to the OTA_AirAvailabilityRS message except it does not contain inventory availability.
OTA_AirSeatMapRQ	OpenTravel Seat Map request.
OTA_AirSeatMapRS	The SeatMap Response message contains the seat map details for the request options given for the requested flight segments. This may include multiple seat maps in case of different seat maps returned for different passengers in the same flight segment.
OTA_AuthorizationRQ	The Authorization message pair verifies and validates a traveler based on information for a bank account, credit card, or driver's license. Each of these can be validated with or without an address.
OTA_AuthorizationRS	Returns authorization or denial for a customer's form of payment.
OTA_CancelRQ	A generic message, available as an action on several OpenTravel services which requests a server to cancel the booking identified by the UniqueID element.
OTA_CancelRS	Used to respond to a CancelRQ and may provide details about the cancellation.
OTA_CodeTables
OTA_CruiseBookingDocumentRQ	This message requests booking related documents and the delivery method for a given Reservation ID.
OTA_CruiseBookingDocumentRS	Provides confirmation that the documents will be delivered as requested.
OTA_CruiseBookingHistoryRS	This message provides a detailed service history for the reservation requested.
OTA_CruiseBookRQ	The book request message requests booking creation on the cruise line system for a given sailing with a specific mode of transportation/ gateway city pair and currency and for a selected fare/category pair and a cabin number. It also integrates this booking into a GDS's PNR based on the cruise line reply. Optional request information can include: Guest city and Inclusive package.
OTA_CruiseBookRS	The book response message contains booking information for a given sailing with a specific mode of transportation/gateway city pair and currency and for a selected fare/category pair. This message contains similar information to a standard airline CRS or GDS sailing availability response message.
OTA_CruiseCabinAvailRQ	The Cabin Availability Request message requests Cabin Availability for a given sailing with a specific Mode of Transportation/GatewayCity pair and currency and for a selected fare/category pair. Optional request information can include: Guest city and Inclusive package.
OTA_CruiseCabinAvailRS	The Cabin Availability Response message contains a list of cabins available for a given sailing with a specific Mode of Transportation/GatewayCity pair and currency and for a selected fare/category pair. For each cabin the following information may be returned: Cabin number; Position in ship; Ship side; Category location; Remark; Deck name; Bed options; Max cabin occupancy; Cabin size; Berthed Category Code; Priced Category Code; Status code; Category indicator; Cruise package information; Group Code; Fare Code; Currency Code; and Marketing message.
OTA_CruiseCabinHoldRQ	The Cabin Hold Request message requests up to four cabins to be held on up to three sailings specific Mode of Transportation/GatewayCity pair and currency and for a selected fare/category pair. Optional request information can include: Guest city and Inclusive package.
OTA_CruiseCabinHoldRS	The cabin hold response message is used to return the list of cabins with the status of thier hold request.
OTA_CruiseCabinUnholdRQ	The Cabin Unhold Request message requests that the specified cabin, currently held for a given sailing, be released back into inventory by the sailing vendor.
OTA_CruiseCabinUnholdRS	The Cabin Unhold Request message requests that the specified cabin, currently held for a given sailing, be released back into inventory by the sailing vendor.
OTA_CruiseCancellationPricingRQ	The cancellation pricing request message is used to price the cancellation penalities if a reservation were to be cancelled.
OTA_CruiseCancellationPricingRS	The cruise cancellation pricing message returns the computed cancellation penalities.
OTA_CruiseCategoryAvailRQ	The Category Availability Request message requests Category Availability for a given sailing with a specific Mode of Transportation/GatewayCity pair and currency and for selected fares (depending on the cruise line). Optional request information can include: Guest ages; Guest city; and Inclusive package.
OTA_CruiseCategoryAvailRS	The Category Availability Response message contains category availability for a given sailing with a specific Mode of Transportation/GatewayCity pair and currency for 1 to multiple fares (depending on the cruise line). For each category the following information may be returned: Berthed category code; Priced category code; Status code; Category indicator; Cruise package information; Group code; Fare code; and Currency code. This message returns the fare amounts available in the different categories. At this point in the process the customer has selected the fare code and has queried the different category offerings for that fare code.
OTA_CruiseDiningAvailRQ	The Dining Availability Request message requests Dining Availability for a given sailing and for selected fares (depending on the cruise line).
OTA_CruiseDiningAvailRS	The Dining Availability Response message contains a list of dinings available for a given sailing and for a selected fare. For each dining the following information may be returned: Dining Code; Dining status; Sittiing; Meal name; Meal times; and Marketing message.
OTA_CruiseFareAvailRQ	The Fare Availability Request message requests Fare Availability for a specific sailing with a specific Mode of Transportation/GatewayCity pair and currency. Optional request information can include: Guest ages and Guest city.
OTA_CruiseFareAvailRS	The Fare Availability Response message contains fares availability for a given sailing with a specific Mode of Transportation/GatewayCity pair and currency. For each fare the following information may be returned: Fare Code; Status code; First and second dining services status; Fare indicator; Alternate available modes of transportation; Alternate available currencies; Cruise package information; and Group Code. This message does not return fare amounts. Fare availability returns the different fare codes that the cruise line uses to group categories. Examples of fare codes are "best fare" or "past passenger fare."
OTA_CruiseFastSellRQ	The Fast Sell Request message requests cabin hold, cabin availability, category availability, and optionally an inclusive package.
OTA_CruiseInfoRQ	Used to request miscellaneous structured cruise information (e.g., cruise ship characteristics, embark/debark time for cruise, cruise policy, cruise line contact).
OTA_CruiseInfoRS	Used to provide miscellaneous structured cruise information (e.g. cruise ship characteristics, embark/debark time for cruise, cruise policy, cruise line contact etc.
OTA_CruiseItineraryDescRQ	The itinerary description request message is used to request the itinerary description on a specific cruise booking.
OTA_CruiseItineraryDescRS	The cruise itinerary description response lists the entire itinerary of a specific sailing and returns detailed information about each location on the itinerary.
OTA_CruisePaymentRQ	This message provides for payments to multiple reservations. It is also a request that can make a payment without needing to retrieve a reservation.
OTA_CruisePaymentRS	This message provides confirmation of payment for each reservation and payment requested.
OTA_CruisePkgAvailRQ	The package availability request message handles pre, post, and inclusive package availability requests for a given sailing.
OTA_CruisePkgAvailRS	The package availability response message contains information about which packages are available for the given sailing.
OTA_CruisePNR_UpdateNotifRQ	PNR Update is an unsolicited message. There are times when a cruise line may change the data related to a booking, and the GDS or agency who holds the booking will be out of sync. This message from the cruise line provides all non-payment information about the booking back to the agency, such as: Guest Personal information; Sailing information; Cabin and Category information; Additional package information; Mode of Transport information; Special service information; Insurance and Dining Information; Gift Information; Cruise profile codes; and Method of payment options.
OTA_CruisePNR_UpdateNotifRS	The PNR update response message is simply an acknowledgement from the Notif recipient indicating they received the Notif message.
OTA_CruisePriceBookingRQ	The Price Booking Request message requests pricing information for a given sailing with a specific Mode of Transportation/ GatewayCity pair and currency and for a selected fare/category pair and a cabin number. Optional request information can include: Guest city and Inclusive package.
OTA_CruisePriceBookingRS	The Price Booking Response message contains pricing information for a given sailing with a specific Mode of Transportation/ GatewayCity pair and currency and for a selected fare/ category pair. This message contains similar information to a standard airline CRS or GDS sailing availability response message.
OTA_CruiseSailAvailRQ	The Sailing Availability Request message requests Sailing Availability for a geographical region on a specific date for a specific number and passengers. Optional request information can include: Cruise lines and Ship codes. The request can be narrowed to request availability for a specific cruise line or specific ship.
OTA_CruiseSailAvailRS	The Sailing Availability Response message contains sailing availability for 1 to many cruise lines for a given region or ship on a date and duration range. For each sailing the following information may be returned: Cruise line code; Ship code; Region code; Departure date; Duration; Voyage number; Number of ports visited; Departure port code; Arrival port code; Status code; Max cabin occupancy; Category location; First and second dining services status; Sailing indicators; Free flow text; Available modes of transportation; Available currencies; Cruise package information; and Registration information. This message contains similar information to a standard airline CRS or GDS sailing availability response message.
OTA_CruiseShorexAvailRQ	The shorex availability request message requests shore excursions for a given sailing and currency.
OTA_CruiseShorexAvailRS	The shorex availability response message contains shore excursion packages that are available for the given sailing/ports.
OTA_CruiseSpecialServiceAvailRQ	The special service availability request message requests special services offered for a given sailing/reservation ID or to request details for a specific special service.
OTA_CruiseSpecialServiceAvailRS	The special service availability response message contains information about which special service packages are available for the given sailing.
OTA_DeleteRQ	A generic message, available as an action on several OpenTravel services which requests a server to delete the business object(s) identified by the UniqueID element(s).
OTA_DeleteRS	Response to a generic OTA_DeleteRQ message, available as an action on several OpenTravel services which requests a server to delete the business object(s) identified by the UniqueID element(s).
OTA_DestActivityCapabilitiesRQ	Sends a request for the functional capabilities of the target system. Following calls (such as resRQ) may be altered depending upon the target system's level of functionality.
OTA_DestActivityCapabilitiesRS	This is used to respond to a CapabilitiesRQ, where the target system responds describing its available level of functionality.
OTA_DestActivityResRQ	Sends a request for a reservation to another system. There is no requirement to determine availability prior to sending a reservation request. Travel agencies, or individual guests may send a request to book a reservation from an internet site if all the information required for booking is known. The OTA_DestActivityResRQ message can initiate the first message in the sequence of booking a reservation.
OTA_DestActivityResRS	This could be used to respond to a OTA_DestActivityResRQ.xsd or the OTA_ReadRQ.xsd. The response to a booking request is either Yes or No based upon the availability. The Destination Activity reservation system responds back attaching a confirmation number or additional information such as the reservation ID, etc. when the response is affirmative.
OTA_DynamicPkgAvailRQ	The Dynamic Package Availability request message is used to obtain availability (with optional pricing) for various components of a dynamic package reservation, that may include Air, Hotel, Car, and Package Options.
OTA_DynamicPkgAvailRS	The AvailPrice response message contains component-specific results for the desired search criteria. This message brings the component-specific response messages together in one location so that partners can receive all required information in one response message.
OTA_DynamicPkgBookRQ	Requests the system to book the specified component itineraries for one or more identified passengers. This message contains identical components to the vertical-specific book request messages (i.e., OTA_AirBookRQ, OTA_HotelResRQ, OTA_VehResRQ).
OTA_DynamicPkgBookRS	Contains the component-specific information sent in the request, along with a unique identifier for the reservation if the booking was successful. In this event, the message also contains component-specific reference numbers at the component level.
OTA_DynamicPkgModifyNotifRQ	This message provides the capability for the Vacation supplier to send notifications of any changes made to the vacation to another system (e.g., a flight is cancelled or moved to a later time, the endpoint system will need to be alerted to the change). This request message is a "push" message.
OTA_DynamicPkgModifyNotifRS	This message acknowledges that the OTA_DynamicPkgModifyNotifRQ has been received.
OTA_DynamicPkgModifyRQ	This is a request message for modifying the components of a dynamic package reservation. When changing data that requires an availability check, this message assumes the availability is known.
OTA_ErrorRS	The standard OTA_ErrorRS message is designed to accommodate errors that result from the parser, or from validation, before reaching the server. The set of errors that can use this error is constrained by its limited structure, to provide structural stability.
OTA_FileAttachmentNotifRQ	The OpenTravel File Attachment Notification message pair enables a sending system to physically transfer encoded binary files to a receiving system that will store or process them. The request message and the encoded files are transferred together in a single encoded entity, with the request message being the first item retrieved by the receiving system. The receiving system uses the request message as a table of contents with the descriptive information it needs to decode and store the files.
OTA_FileAttachmentNotifRS	The File Attachment Notif response message is used to acknowledge receipt of the request.
OTA_GolfCourseAvailRQ	The Golf Tee Time Availability requests availability for specified golf facility(s) and optional tee time(s). Golfer information must be provided and optional discount/promotion and requested amenities may be specified to validate booking rules and establish tee time pricing. Additional message functionality includes transaction processing directives that influence search results, such as display currency and maximum quantity of results. Developer Notes: The ID of a golf facility is required to request tee time availability.
OTA_GolfCourseAvailRS	The Golf Tee Time Availability response provides availability for specified golf facility(s) and tee time(s). Additional message functionality includes transaction processing directives that influence search results, such as display currency and maximum quantity of results. Developer Notes: » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_GolfCourseResModifyRQ	The Golf Course Reservation Modification request provides the information required to modify an existing (booked) tee time reservation for one or more golfers. Note that the response message for this request is the OTA_GolfCourseResRS message.
OTA_GolfCourseResRQ	The Golf Course Reservation request provides the information required to book a tee time reservation for one or more golfers. Booking information includes: » An internal reference number for the requested booking » Round and Package ID » Start date, time and duration for the tee time » Detailed or summary information about the golfers » Charges for the tee time » Payment form details for the tee time » Discounts requested for the tee time » Amenities requested for the tee time » Commissions that apply to the booking
OTA_GolfCourseResRS	The Golf Course Reservation response provides the information required to confirm a tee time reservation for one or more golfers. Booking information includes: » An internal reference number for the requested booking » Round and Package ID » Start date, time and duration for the tee time » Detailed or summary information about the golfers » Charges for the tee time » Payment form details for the tee time » Discounts requested for the tee time » Amenities requested for the tee time » Commissions that apply to the booking » Facility details Developer Notes: » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_GolfCourseSearchRQ	The Golf Course Search request sends search criteria for golf facility(s), which may be a golf course proper and/or a facility such as a hotel that has an association with a nearby golf course or a course on premise. Supported search functionality includes: » Search by facility ID and/or name » Search by course location (street, city, state, county, country, postal code) » Search by geo-coded position » Search by proximity (location and maximum distance) » Search by maximum tee time fee » Search by facility amenities (golf carts, driving range, etc.) Additional message functionality includes: » Transaction processing directives to influence and or constrain search results, such as display/ pricing currency, redemption currency indicator and the maximum search results in the response » Point of sale information for the requestor and booking channel Developer Notes: » Note that this message pair is intended for a high level search of golf facility(s) and is not intended to be used for specific tee time search or availability. » Implementers should check with their trading partner(s) to determine the golf facility search capabilities supported by their system(s).
OTA_GolfCourseSearchRS	The Golf Course Search response sends results based on specified search criteria for golf facility(s), which may be a golf course proper and/or a facility such as a hotel that has an association with a nearby golf course or a course on premise. Response information includes: » Facility ID, name and associated facility (if the course is on a hotel property) » Short and long descriptions (with optional club type) » Contact information, including phone and website » Multimedia, including images, descriptions and movies that describe the golf facility » Facility features, including dress policy, golf pros, on facility dining and course designer » Available amenities, including type, description, pricing and reservation information » Guideline tee time pricing, including minimum, maximum and average » Location information, including physical and geo-coding » Hours of operation » Course conditions, including an optional source name or URL » Policy information » Directions » Course closures » Course restrictions » Course scorecard Additional message functionality includes transaction processing directives that influenced search results, such as display currency. Developer Notes: » Note that this message pair is intended for a high level search of golf facility(s) and is not intended to be used for specific tee time search or availability. » Implementers should check with their trading partner(s) to determine the golf facility search capabilities supported by their system(s). » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_GolfFacilityInfoRQ	The Golf Facility Information request sends a request for updated golf course facility information which is used to keep trading partner database(s) and cache(s) current with golf supplier facility information. Golf facility request information includes the ID and (optional) name of the golf course facility, which may be repeated to request information about multiple courses.
OTA_GolfFacilityInfoRS	The Golf Facility Information response returns detailed golf facility information for the specified facility ID(s). Response information includes: » Facility ID, name and associated facility (if the course is on a hotel property) » Short and long descriptions (with optional club type) » Contact information, including phone and website » Multimedia, including images, descriptions and movies that describe the golf facility » Facility features, including dress policy, golf pros, on facility dining and course designer » Available amenities, including type, description, pricing and reservation information » Guideline tee time pricing, including minimum, maximum and average » Location information, including physical and geo-coding » Hours of operation » Course conditions, including an optional source name or URL » Policy information » Directions » Course closures » Course restrictions » Course scorecard Additional message functionality includes transaction processing directives that influenced search results, such as display currency. Developer Notes: » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_GolfRatePlanRS	This message returns information about golf rate plans that meet the requested criteria.
OTA_GolfRateRQ	This message provides the ability to request rate plan details for golf facility(s) and tee time(s) by specific criteria that may include dates, date ranges, and rate qualifiers.
OTA_GroundAvailRQ	The OpenTravel Ground Transportation availability request message queries a suppliers system for service availability that matches specified search criteria. Search criteria options include: -Type of service-including airport and simple transfers -Date and time of required service -Pickup, stops and drop-off details -Passenger and baggage quantities -Special requirements-including child car seats, fuel efficient vehicle, meet and greet, pet friendly and disability equipped vehicle request -Rate qualifying information-including promotions and corporate accounts -Vehicle type-including limousine and luxury sedan.
OTA_GroundAvailRS	The OpenTravel Ground Transportation availability response message returns supplier availability that matches specified search criteria. This message may include a success element (and/or business warnings) with availability details or an error message indicating why the message could not be processed. Availability response information includes: -Service information (including service type, vehicle type, disability equipped vehicle indicator and recommended maximum passengers and baggage) -Vehicle make and model information -Rate qualifying information associated with the vehicle and/or ground transportation service -Restrictions that apply to the vehicle and/or ground transportation service, such as advanced booking, guarantees and cancellation/ modification penalty indicators -Service charges, including taxes, minimum and maximum charges, and service charge calculation details -Fees that may be applied in addition to the Ground Transportation Service charges -Estimated total charges -Service availability reference ID/number -Payment rules that are applicable to a specific vehicle or ground service type
OTA_GroundBookRQ	The OpenTravel Ground Transportation reservation (booking) request message includes the information required to create one ground transportation reservation that may have multiple segments associated with it. Reservation request information includes: -Point of sale information for the requestor -Availability reference ID (A reference ID that was returned in a prior availability response message and may be used to reduce the amount of duplicate information in this request) -Service locations, that include pickup, stop(s) and drop-off details -Primary passenger and additional passenger contact information -General passenger information that may determine the class of vehicle required -Passenger preferences (including service type, vehicle type, disability equipped vehicle indicator and recommended maximum passengers and baggage) -Rate qualifying information associated with the vehicle and/or ground transportation service -Payment rules that are applicable to a specific vehicle or ground service type
OTA_GroundBookRS	The OpenTravel Ground Transportation reservation (booking) response message may include a success element (and/or business warnings) with reservation details or an error message indicating why the message could not be processed. Reservation response information includes: -A confirmation number for the successfully booked ground transportation service reservation -Information about a primary passenger (who is the contact for this reservation) and additional passengers associated with the reservation -Information about the locations associated with the reservation, including pickup, interim stop(s) and drop-off details -Vehicle make and model information associated with this reservation -Rate qualifying information associated with the vehicle and/or ground transportation service reservation -Service charges, including taxes, minimum and maximum charges, and service charge calculation details -Fees that may be applied in addition to the Ground Transportation Service charges -Estimated total charges -Restrictions that apply to this vehicle/ ground transportation service reservation -Payment rules that are applicable to this ground service reservation -Comments associated with this reservation
OTA_GroundCancelRQ	The Ground Cancel message requests the cancellation of one confirmed ground reservation. The CancelType (e.g. Cancel or Hold) and a minimum of one unique ID's (typically the booking confirmation number of the reservation to be canceled) are required.
OTA_GroundCancelRS	This message acknowledges that the ground reservation cancel message was received and processed successfully and/or has returned business warnings. If processed successfully, one or more Cancellation ID's will be returned with optional cancellation rules information and other details about the canceled reservation.
OTA_GroundModifyRQ	The OpenTravel Ground Transportation modify reservation (booking) request message includes the information required to change an existing ground transportation reservation. Note that the response for this modification is the OTA_GroundBookRS message.
OTA_GroundResNotifRQ	The OpenTravel Ground Transportation reservation (booking) notification request message is designed to be used as an unsolicited push notification message between IT systems and/or trading partners. This message includes the information required to create or store details for one ground transportation reservation that may have multiple segments associated with it. Exchanged reservation information includes: -Confirmation number(s) for the successfully booked ground transportation service reservation -Information about the primary passenger (who is the contact for this reservation) and additional passengers associated with the reservation -Information about the locations associated with the reservation, including pickup, interim stop(s) and drop-off details -Vehicle make and model information associated with the reservation -Rate qualifying information associated with the vehicle and/or ground transportation service reservation -Service charges, including taxes, minimum and maximum charges, and service charge calculation details -Fees that were applied in addition to the Ground Transportation Service charges -Estimated total charges -Restrictions that apply to the ground transportation service reservation -Payment rules that were applicable to the ground service reservation -Comments associated with the reservation
OTA_GroundResNotifRS	This message acknowledges that the ground reservation notification message was received and processed successfully and/or has returned business warnings.
OTA_GroundResRetrieveRQ	The OpenTravel Ground Transportation reservation request is used to specify criteria to retrieve an existing ground transportation reservation, which may include a unique ground transportation reservation identifier (which if valid will return one matching reservation) or general search criteria for a reservation (which if valid may return one or more reservations that matched the search criteria.) Reservation retrieve request information includes: -Point of sale information for the requestor -A choice between entering a known ground transportation service reservation identifier used to return one exact matching reservation -OR- basic search criteria used to retrieve one or more matching reservations ----A reference ID for the existing ground transportation reservation ----Search criteria that can be used to retrieve an existing ground transportation reservation if the reservation ID/reference number is not known, including passenger name/contact information and rate qualifiers associated with the reservation
OTA_GroundResRetrieveRS	The Ground Transportation Retrieve Reservation response is used to return either an exact match for one reservation (typically when a valid reservation reference ID/number has been specified) -OR- a list of reservations that match the criteria specified in the Ground Transportation Reservation Retrieve request message. This message may include a success element (and/or business warnings) with reservation details or an error message indicating why the message could not be processed. If reservation search criteria has been specified, the Reservations element may contain multiple matching reservations. Returned information includes: -A confirmation number for the ground transportation service reservation -Information about a primary passenger (who is the contact for the reservation) and additional passengers associated with the reservation -Information about the locations associated with the reservation, including pickup, interim stop(s) and drop-off details -Vehicle make and model information associated with the reservation -Rate qualifying information associated with the vehicle and/or ground transportation service reservation -Service charges, including taxes, minimum and maximum charges, and service charge calculation details -Fees that may be applied in addition to the Ground Transportation Service charges -Estimated total charges -Restrictions that apply to the vehicle and/or ground transportation service reservation -Payment rules that are applicable to the ground service reservation -Comments associated with the reservation
OTA_HotelAvailGetRQ	Provides the ability to request availability details for hotel properties by specific criteria that may include dates, date ranges, rates, rooms and products.
OTA_HotelAvailGetRS	Returns information about hotel availability that meet the requested criteria.
OTA_HotelAvailNotifRQ	The OTA_AvailNotifRQ is the message that sends the notification of the availability status of a hotel.
OTA_HotelAvailNotifRS	The OTA_HotelAvailNotifRS is the message used to indicate the status of processing the OTA_HotelAvailNotifRQ message.
OTA_HotelAvailRQ	Requests availability of hotel properties by specific criteria that may include: dates, date ranges, price range, room types, regular and qualifying rates, and/or services and amenities. The availability message can be used to get an initial availability or to get availability for the purpose of modifying an existing reservation.
OTA_HotelAvailRS	Returns information about hotel properties that meet the requested criteria, indicating whether the requested service, rate, room stay, etc. is available within the date(s) specified. The response message may include Warnings from business processing rules, or Errors if the request did not succeed.
OTA_HotelBookingRuleNotifRQ	The OTA_BookingRuleNotifRQ is the message that sends the notification of the rules and restrictions affecting the availability status of the hotel.
OTA_HotelBookingRuleNotifRS	The OTA_HotelBookingRuleNotifRS is the message used to indicate the status of processing the OTA_HotelBookingRuleNotifRQ message.
OTA_HotelBookingRuleRQ	This message provides the capability of requesting the rules and usage requirements (either all or for a specific rule category) of a rate for a specific hotel property. The request may be per room type, booking code, check in/out dates, or by confirmation number for a previously booked reservation.
OTA_HotelBookingRuleRS	This message will provide the rule details for a specific hotel based on the room type, booking code, checkin/out dates or a confirmation number.
OTA_HotelCacheChangeNotifRQ	The OpenTravel Hotel Cache Change Notification message set allows a hotel supplier to push their changed hotel rates and availability information to a trading partner that caches their hotel rates and availability information and have the trading partner send an acknowledgement message that they received the information. Note that this message set is designed to allow the trading partner to receive the changed rates and availability information from the supplier so the trading partner can create a subsequent targeted Hotel Availability Request message that only requests the specific supplier data that has changed and needs to be updated in the trading partner cache. Hotel Cache Change Notification Request information includes: -Point of sale information for the requestor -Unique identifier information that allows trading partners to uniquely identify each Hotel Cache Change Notification Request message for transaction tracing purposes -Destination system information that specifies a receiving system for the message information -Cache change information-which specifies what hotel supplier data has changed and should be updated in the trading partners system via a subsequent OTA_HotelAvailRQ message-including: ----Chain, brand and hotel codes ----The start and end date of information that should be updated in the cache for the associated @HotelCode and an optional "change date mask" that indicates if there are changes in all or a portion of the returned date range; including Length of stay that indicates how many days of availability from start date should be shopped; and Full Pattern Length Of Stay to indicate which days from start date should be shopped ----Other changed product details, including rate plan and promotion details
OTA_HotelCacheChangeNotifRS	The Hotel Cache Change Notification Response message may return: -A success indicator (indicating that the message was successfully received and processed) -A business warning (indicating that some portion of the message processing generated a business condition) -An error response that may indicate why the message could not be processed)
OTA_HotelCacheChangeRQ	This message provides request functionality for querying a trading partners system for hotel inventory items that have availability and/or rate changes and therefore should be updated in a trading partner's cache. The information in the response message will indicate if an OTA_HotelAvailRQ is required to refresh the trading partner's data cache.
OTA_HotelCacheChangeRS	This message provides response functionality from a query of a trading partners system for hotel inventory items that have availability and/or rate changes and therefore should be updated in a trading partner's cache. The information in this response message will indicate if an OTA_HotelAvailRQ is required to refresh the trading partner's data cache.
OTA_HotelCommNotifRQ	CommissionEventUpdateRequest: CommissionsEvents are prepared by the PMS as a result of a guest stay, or by systems such as an activity vendor's system as a result of a completed activity. The report is then sent to the entity responsible for making payments to those parties that are to receive commissions for the transactions.
OTA_HotelCommNotifRS	The OTA_HotelCommNotifRS is the message used to indicate the status of processing the OTA_HotelCommNotifRQ message.
OTA_HotelDescriptiveContentNotifRQ	The Hotel Descriptive Content Notification is a broadcast message used to publicize detailed descriptive information about a hotel property by standardized data categories. Likewise, static information about a hotel property can be obtained by using the Hotel Search Request and/or Hotel Availability Request to search for static information by category, using codes agreed upon between trading partners to request more detail about a hotel. The Hotel Descriptive Content interface enables accessing hotel data in both a push and pull format in order to avoid storing the data at multiple locations. In most cases, the hotel property is the owner of the data and is in charge of updating it, and sends out a broadcast message as a full overlay replacing previous information or a partial update message modification to make changes or portions of the data.
OTA_HotelDescriptiveContentNotifRS	The OTA_HotelDescriptiveContentNotifRS is the message used to indicate the status of processing the OTA_HotelDescriptiveContentNotifRQ message.
OTA_HotelDescriptiveInfoRQ	The OTA_HotelDescriptiveInfoRQ message allows a trading partner to query for specific hotel descriptive data.
OTA_HotelDescriptiveInfoRS	The Hotel Descriptive Info Response is a message used to provide detailed descriptive information about a hotel property.
OTA_HotelEventRQ	This message communicates the meeting planners event needs to an event host facility (ies). This includes needs ranging from meeting room setup, audiovisual, catering, safety and security among other meeting and event requirements.
OTA_HotelEventRS	This message is used to confirm receipt of a hotel event request.
OTA_HotelGetMsgRQ	Sends a request to another system to permit a system that normally receives notifications to ask for a re-transmission of a message. The business model assumes that the requesting system either receives messages that are numbered sequentially, and may ask for a message to be re-sent. In the event that the receiving system receives a message that is not in contiguous numerical sequence, this message set can be used to retrieve missing messages, or to ask for a retransmission of data that for some reason was not cleanly received.
OTA_HotelGetMsgRS	Returns acknowledgement that the request has been successfully received, or includes Warnings from business processing rules or errors if the request did not succeed. It will additionally include the re-submission of the requested data as it was sent in its original form. Since the request could be for any original message, the response data is included in MessageContent.
OTA_HotelInvAdjustRQ
OTA_HotelInvAdjustRS
OTA_HotelInvBlockNotifRQ	The OTA_InvBlockNotifRQ may be used to send a notification of one or more new inventory blocks. This message may also be used to modify or cancel one or more existing inventory blocks.
OTA_HotelInvBlockNotifRS	The OTA_HotelInvBlockNotifRS message returns an indication of the status of processing the OTA_HotelInvBlockNotifRQ message.
OTA_HotelInvBlockRQ	This message provides the ability to request inventory block details for hotel properties by specific criteria that may include dates, date ranges, rooms and products.
OTA_HotelInvBlockRS	This message returns information about inventory count that meet the requested criteria.
OTA_HotelInvCountNotifRQ	This message sends a notification to reservation systems that synchronizes the inventory available for sale at the hotel.
OTA_HotelInvCountNotifRS	This message is used to indicate the status of processing the OTA_HotelInvCountNotifRQ message.
OTA_HotelInvCountRQ	This message provides the ability to request inventory count details for hotel properties by specific criteria that may include dates, date ranges, rooms and products.
OTA_HotelInvCountRS	This message returns information about inv count that meet the requested criteria.
OTA_HotelInvNotifRQ	The OTA_HotelInvNotifRQ is the message that sends the notification of a new inventory item, such as a room type or service type created for the hotel that did not previously exist.
OTA_HotelInvNotifRS	The Hotel Inventory Notification Response message returns the status of processing an Inventory Notification message, and optionally returns a cross-reference of the inventory codes received.
OTA_HotelInvSyncRQ
OTA_HotelInvSyncRS
OTA_HotelPostEventNotifRQ	This message communicates the actual history of one or more events.
OTA_HotelPostEventNotifRS	This message acknowledges the receipt of a post event report notif request message.
OTA_HotelPostEventRQ	This message may be used to request post event information for one or more events for one or more sites. It may also be used to request one or more post event report(s) for one or more sites.
OTA_HotelPostEventRS	This message communicates the actual history of one or more events.
OTA_HotelProductNotifRQ	The OTA_HotelProductNotifRQ may be used to send a notification of one or more new hotel products. This message may also be used to modify or cancel one or more existing hotel products.
OTA_HotelProductNotifRS	This message acknowledges the receipt of a OTA_HotelProductNotifRQ mesaage.
OTA_HotelProductRQ	Requests product information for one or more hotel properties by specific criteria.
OTA_HotelProductRS	Returns information about hotel products that meet the requested criteria. The response message may include Warnings from business processing rules, or Errors if the request did not succeed.
OTA_HotelRateAmountNotifRQ	This message is used to provide a notification of a new rate plan created for a hotel, and to synchronize the rate plan between systems for booking.
OTA_HotelRateAmountNotifRS	This message is used to indicate the status of processing the OTA_HotelRateAmountNotifRQ message.
OTA_HotelRatePlanNotifRQ	This message sends the notification of a new Rate Plan.
OTA_HotelRatePlanNotifRS	This message returns an integer to indicate the status of processing the OTA_HotelRatePlanNotifRQ message.
OTA_HotelRatePlanRQ	This message provides the ability to request rate plan details for hotel properties by specific criteria that may include dates, date ranges, and rates.
OTA_HotelRatePlanRS	This message returns information about hotel rate plans that meet the requested criteria.
OTA_HotelResModifyNotifRQ	This is a notification request message (push message) for reservations that were modified. It is used for a full overlay of the reservation. When changing data that requires an availability check, this message assumes the availability is known (if availability is not known an availability check containing the reservation ID may be useful).
OTA_HotelResModifyNotifRS	This is the response notify message for a full overlay modification to a reservation. The response could be as simple as indicating the modification was made or as complex as echoing back all reservation information.
OTA_HotelResModifyRQ	This is a request message for modifying a reservation. It is used for a full overlay of the reservation. When changing data that requires an availability check, this message assumes the availability is known (if availability is not known an availability check containing the reservation ID may be useful).
OTA_HotelResModifyRS	This is the response message for a full overlay modification to a reservation. The response could be as simple as indicating the modification was made or as complex as echoing back all reservation information.
OTA_HotelResNotifRQ	This message supports the functionality of updating other systems with reservation data. The message assumes a push model, with the originating system pushing the data to another system. The originating system would usually be a booking source, such as a Global Distribution System (GDS), a Central Reservation System (CRS) or some other agent of the hotel.
OTA_HotelResNotifRS	This message returns acknowledgement that the reservation has been successfully received, or includes warnings from business processing rules or errors if the request did not succeed. It may optionally include the updated reservation data.
OTA_HotelResRQ	This message sends a request for a reservation to another system.There is no requirement to determine availability prior to sending a reservation request. Travel agencies, or individual guests may send a request to book a reservation from an internet site if all the information required for booking is known. The OTA_HotelResRQ message can initiate the first message in the sequence of booking a reservation.
OTA_HotelResRS	This message could be used to respond to a OTA_HotelResRQ.xsd or the OTA_ReadRQ.xsd. The response to a booking request is either Yes or No based upon the availability. The hotel PMS or CRS system responds back attaching a confirmation number or additional information such as the reservation ID, etc. when the response is affirmative. Additional information, such as the count of Loyalty Program miles or points to be awarded for the hotel stay, can be added to the Reservation object in the return. Supplementary data for the reservation can be added later, once the reservation has been confirmed and the inventory held.
OTA_HotelRFP_MeetingNotifRQ	The OTA_HotelRFP_NotifRQ sends detailed information as previously requested via an OTA_HotelRFP_RQ or sent unsolicitated with updated information regarding an RFP. The response to this message would be the OTA_AcknowledgementRS.xsd.
OTA_HotelRFP_MeetingNotifRS	This is a generic acknowledgement response message that may be used with various OpenTravel request messages. This simply acknowledges that the request message was received.
OTA_HotelRFP_MeetingRQ	This message is used to request a block of rooms and/or meeting space for one or many sites.
OTA_HotelRFP_MeetingRS	This message acknowledges that the OTA_HotelRFP_MeetingRQ message was received.
OTA_HotelRFP_TransientNotifRQ	The transient RFP supports the buyer to supplier process of negotiating room rates and amenities for a given contract period. The buyer is the corporation negotiating directly with the supplier-- example, hotel chains or individual hotels.The OTA_HotelRFP_TransientNotifRQ is sent by the hotelier. The response sends detailed information as previously requested or updated information regarding a RFP.
OTA_HotelRFP_TransientNotifRS	The transient RFP supports the buyer to supplier process of negotiating room rates and amenities for a given contract period. The buyer is the corporation negotiating directly with the supplier-- example, hotel chains or individual hotels.The OTA_HotelRFP_TransientNotifRS acknowledges receipt of the OTA_HotelRFP_TransientNotifRQ.
OTA_HotelRFP_TransientRQ	This message is used to request a business rate for a specific account for one or many locations.
OTA_HotelRFP_TransientRS	This is an acknowledgement that the OTA_HotelRFP_TransientRQ message was received and/or a full response.
OTA_HotelRoomListRQ	The OTA_HotelRoomListRQ message applies to the group (meetings and conventions) market and the tour (wholesale) market. In both cases, travelers' reservations are booked into blocked space, instead of publicly available room inventory. This message provides the details of the individual guests staying in the blocked rooms.
OTA_HotelRoomListRS	The OTA_HotelRoomListRS message contains confirmation numbers and possibly echo back the reservation details for each guest in the room list(s).
OTA_HotelSearchRQ	This message identifies the initial request for hotel property data.
OTA_HotelSearchRS	This message returns a list of hotel properties that meet the requested criteria and/or Warnings, or Errors if the request did not succeed.
OTA_HotelStatsNotifRQ	The Statistic Notification Request is a report that may be generated at regular intervals by the property management system (PMS) and sent to a chain, central reservation office (CRO), or management company system. It provides an update of hotel statistics for analysis and may be sent unsolicited by the PMS to the receiving system.
OTA_HotelStatsNotifRS	This message is used to indicate the status of processing the OTA_HotelStatsNotifRQ message.
OTA_HotelStatsRQ	This message is sent by a system (e.g. RMS) requesting one or several pre-defined statistic reports for one or several hotels from another system (e.g. CRS) which has the data required to generate the reports.
OTA_HotelStatsRS	This message is returned by the sytem that received an OTA_HotelStatsRQ message. If sucessful, it includes one or more of the pre-defined reports requested.
OTA_HotelStayInfoNotifRQ	This message broadcasts guest stay information to the Central Reservation System or the hotel management company. It is sent unsolicited as an update of guest data and provides a snapshot of individual guest records.
OTA_HotelStayInfoNotifRS	This message is used to specify the status of the processing of the OTA_HotelStayInfoNotifRQ message. This message also allows the responder to return additional information regarding the processing of the stay information that was received.
OTA_HotelSummaryNotifRQ	This message sends the notification of the general availability of a hotel for booking.
OTA_HotelSummaryNotifRS	This message is used to indicate the status of processing the OTA_HotelSummaryNotifRQ message.
OTA_InsuranceBookRQ	This message contains the container for insurance plan book requests.
OTA_InsuranceBookRS	This message contains the container for insurance plan book responses.
OTA_InsurancePlanSearchRQ	This message contains the root element for insurance plan search request.
OTA_InsurancePlanSearchRS	This message contains the root element for insurance plan search response message
OTA_InsuranceQuoteRQ	This message is the container for insurance quote requests.
OTA_InsuranceQuoteRS	This message contains the container for insurance plan quote results.
OTA_LoyaltyAccountCreateRQ	The message set will allow businesses to send enrollment information to their loyalty service provider to create a new account for one of their customers. This message will be based on the profile structure (OTA_Profile.xsd) with extensions for information that pertains only to loyalty account creation. In response, a message containing the newly created account information (e.g. membership ID) would be returned.
OTA_LoyaltyAccountRS	This message may be used to respond to a loyalty account create request or a loyalty account read request.
OTA_LoyaltyCertificateCreateNotifRQ	The CertificateCreateNotifRQ allows loyalty service provider to communicate to business that a redemption certificates has been created.
OTA_LoyaltyCertificateCreateNotifRS	The CertificateCreateNotifRS confirms receipt of the creation notification.
OTA_LoyaltyCertificateCreateRQ	The CertificateCreateRQ allows businesses to communicate with their loyalty service provider to generate redemption certificates for their customers.
OTA_LoyaltyCertificateCreateRS	The CertificateCreateRS allows businesses to communicate with their loyalty service provider to generate redemption certificates for their customers.
OTA_LoyaltyCertificateRedemptionRQ	The CertificateRedemptionRQ allows businesses to communicate with their loyalty service provider to redeem certificates or points for their customers.
OTA_LoyaltyCertificateRedemptionRS	The CertificateRedemptionRS allows loyalty service providers to respond to a request for a certificate or points redemption.
OTA_NotifReportRQ	This message is used to indicate the status of processing one or several previous messages.
OTA_NotifReportRS	This message is used to acknowledge reception of an OTA_NotifReportRQ message.
OTA_PingRQ	The OpenTravel Ping message pair are used to test application connectivity by sending some specific text and determining if the receiving application is able to echo back that same text. The free-text data that is passed in the request is expected to be echoed back in the response message.
OTA_PingRS	The Ping response message is a response to a client message used for testing application connectivity. Specific text sent by the client is to be echoed back in this response.
OTA_PkgAvailRQ	A request for availability of a specific package.
OTA_PkgAvailRS	The message details the availability of a requested package.
OTA_PkgBookRQ	A message to request a package holiday booking.
OTA_PkgBookRS	Confirmation of a package booking.
OTA_PkgCostRQ	A request for a costing of a specific profile of a package.
OTA_PkgCostRS	The message returns a basic costing for a requested package.
OTA_PkgExtrasInfoRQ	A request for a details of the extras available with a package, optionally modified by the profile of the passengers.
OTA_PkgExtrasInfoRS	The message returns package extras and/or car rental information for a specific package.
OTA_ProfileCreateRQ	Provides the ability to create a new profile.
OTA_ProfileCreateRS	Provides the IDs resulting from the creation of a new profile.
OTA_ProfileMergeRQ	This message provides for the merging of one or more profiles.
OTA_ProfileMergeRS	This message provides the acknowledgement of a merge request.
OTA_ProfileModifyRQ	This is a request message for modifying a profile identified by UniqueID. It is used for a full overlay of the profile.
OTA_ProfileModifyRS	This message provides the acknowledgement of a profile modification request.
OTA_ProfileReadRS	Returns a single or multiple customer profile(s) in response to a ReadRQ request of Type=Profile.
OTA_PurchaseItemRQ	The OpenTravel Purchase Item message pair provides functionality for electronic purchases of non-inventory items (e.g. gift certificates for a hotel, drink tickets on an airline, etc.) The message pair supports the ordering process with detailed product, recipient, purchaser and payment information.
OTA_PurchaseItemRS	This message provides information confirming the receipt of a purchase item request.
OTA_RailAvailRQ	The rail availability request message requests train availability for a station pair on a specific date for a specific number and type of passengers. Optional request information can include: time and flexible time windows, connecting cities and client preferences. Additionally, this request can be narrowed to request availability for a specific train.
OTA_RailAvailRS	The Availability Response message contains train vvailability for a station on a specific date. A set of OriginDestinationOptions is returned, each of which contains one or more (connecting) trains that serve the city pair. The response comprises a list of available train departures from the Origin to the Destination and, where the responding system has this facility, valid fares available on those departures.
OTA_RailBookModifyRQ	The Rail Book Modify request message is used to request that a reservation be created for one or more rail journies between specified locations on specific date(s) for a specific number and type of passengers. NOTE that a subsequent OTA_RailConfirmBookingRQ message is required to acquire a PNR for the reservation, or an OTA_RailIgnoreBookingRQ message is required to release the reservation (and associated inventory) from the trading partner system.
OTA_RailBookRQ	The Rail Book request message is used to request that a reservation be created for one or more rail journies between specified locations on specific date(s) for a specific number and type of passengers. NOTE that a subsequent OTA_RailConfirmBookingRQ message is required to acquire a PNR for the reservation, or an OTA_RailIgnoreBookingRQ message is required to release the reservation (and associated inventory) from the trading partner system.
OTA_RailBookRS	The OTA_RailBookRS element in this message defines the response to a request to create a rail reservation. This response contains: - Full rail itinerary details, including origin and destination location details (including departure and arrival station, marketing and operating companies, equipment, train identification and classification, inventory class codes, accommodation details, ancillary services, charges and vendor messages) - Passenger information - Payment rules - Fulfillment details NOTES: A subsequent OTA_RailConfirmBookingRQ message is required to acquire a booking ID for the reservation, or an OTA_RailIgnoreBookingRQ message is required to release the reservation (and associated inventory) from the trading partner system. This message contains ONE instance of a rail reservation and is not recommended for use as a response message to a Rail Reservation Read request (OTA_RailReadRQ).
OTA_RailConfirmBookingRQ	The Rail Confirm Booking RQ message is the request message to commit one or more provisionally booked messages that have been processed successfully from an OTA_RailBookRQ message but are not yet confirmed in the trading partners system. Successful processing of this message results in PNR creation.
OTA_RailConfirmBookingRS	The Rail Confirm Booking RS message is the response message for an OTA_RailConfirmBookingRQ that commits one or more provisionally booked messages that have been processed successfully from an OTA_RailBookRQ message but are not yet confirmed in the trading partners system as booked. If the request message has been processed successfully, the Confirmation element in this response message contains the PNR Locator list that contains only unique ID(s) –OR- unique ID(s) with corresponding reservation information. NOTE that this is an implementation detail that you should discuss with your trading partners prior to implementing this message.
OTA_RailFareQuoteRQ	The OpenTravel Rail Fare Quote request message is used to request rail fare option information based on specified criteria including: - Qualifying fare options (including train type, origin/destination locations, arrival/departure times and/or train number and network codes) - Up to 9 fare basis codes - Traveler preferences (including accommodation and class codes) - Rate qualifying information (including travel purpose, promotion codes and other discounts that may affect the fare) - Passenger category information (by passenger quantity, including gender, occupation, passenger qualifying codes, rate qualifiers and disability requirements)
OTA_RailFareQuoteRS	The Rail Fare Quote Response may return: - A success indicator with rail fare quote details - A business warning with or without rail fare quote details - An error response (indicating why the message could not be processed) with no rail fare quote details as the request has not been processed If successfully processed, the Rail Fare Quote Response information includes: - Origin and destination location for the entire fare quote - Fare owner details for the entire fare quote - Fares details including: ---Train type ---Start and end dates for the fare quote ---Blockout dates indicator ---Class codes for inventory controlled items ---Seat, berth and compartment class details ---Up to 99 origin/destination pairs associated with the fare quote ---Fare basis code(s) and associated fare amount(s) ---Terms and conditions associated with the fare quote - Notes related to all fare information returned
OTA_RailIgnoreBookingRQ	The Rail Ignore Booking RQ message is the request message to cancel one or more provisionally booked messages that have been processed successfully from an OTA_RailBookRQ message but are not yet confirmed in the trading partners system. Successful processing of this message results in information pertaining to the associated reservations that have been cancelled.
OTA_RailIgnoreBookingRS	The Ignore Booking response message is the response message for an OTA_RailIgnoreBookingRQ that CANCELS booking messages that may have been processed successfully but are not confirmed in the trading partners system as booked. If the request message has been processed successfully, the Confirmation element contains the Unique ID's and optional details for the ignored reservations.
OTA_RailPaymentRQ	The Rail Payment request message is used to submit a payment for a reservation. This request message typically follows the combination of OTA_RailBookRQ and OTA_RailConfirmBookingRQ messages.
OTA_RailPaymentRS	The Rail Payment response message includes the reservation ID (e.g. the confirmation number of a PNR locator) and indicates whether or not the Rail Payment request message has been processed successfully.
OTA_RailPriceRQ	The OpenTravel Rail Price request message is used to request rail itinerary pricing information for a specified origin/destination pair –and- specified passenger information, including passenger type, rate qualifier(s) and other passenger details. Note that you may request pricing information by supplying passenger information AND: Rail itinerary information (including Origin/Destination location details and train segment information) -OR- Booking Reference information (including the PNR address of the booking which needs to be priced, train segments that have already been booked and a fare basis code to be used to price the train segments in the PNR. Additional price qualifier information that may be supplied includes: Rate qualifier information for ALL travelers (including travel purpose, promotion codes and rate category that may affect the fare) and Payment form information (including form of payment to be used to pay for the reservation.)
OTA_RailPriceRS	The OpenTravel Rail Price response message may return: - A success indicator with rail price details - A business warning with or without rail price details - An error response (indicating why the message could not be processed) with no rail price details as the request has not been processed If successfully processed, the Rail Price response information includes a priced itinerary with some or all of the following information: - Pricing information for a rail itinerary, including the total price for the rail itinerary and pricing details, e.g. summary or detailed basic fare, discounts, service charges, fare adjustments, fees and taxes. - Journey information from one specific origin to one specific destination, including train segment and pricing details - Passenger information, including occupation, age qualifier, disability, loyalty program, personal identification and contact information - Notes associated with the priced itinerary
OTA_RailReadRQ	The read request message is used to retrieve reservation either by the confirmation number or by specifying point of sale, train, traveler or booking/departure date and time criteria. NOTES: - Summary rail reservation information is typically returned in the OTA_RailResRetrieveSummaryRS message if the @ResInfoLevel is Summary - Detailed reservation information (including full itinerary) is typically returned in the OTA_RailResRetrieveDetailRS message if the @ResInfoLevel is Detailed - In some cases, a rail supplier may return the OTA_RailBookRS message as a response to a Read Rail Reservation request - CHECK WITH YOUR TRADING PARTNER to determine their specific implementation
OTA_RailResRetrieveDetailRS	This message returns detailed information about an existing rail reservation for an exact match on a read request that includes: - Full rail itinerary details, including origin and destination location details (including departure and arrival station, marketing and operating companies, equipment, train identification and classification, inventory class codes, accommodation details, ancillary services, charges and vendor messages) - Passenger information - Payment rules - Fulfillment details NOTES: - For summary rail reservation information on an exact match of a read request, or multiple matches on a read request, the OTA_RailResRetrieveSummaryRS message is typically returned. - Check with your trading partner to confirm their implementation of the Rail Read Reservation response messages.
OTA_RailResRetrieveSummaryRS	This message returns a list of summary reservation(s) information when an exact match on a read request could NOT be made or if summary reservation response information was specifically requested in the OTA_RailReadRQ @ResInfoLevel attribute. Summary reservation information in this message includes: - Reservation booking reference, date and status - Origin and destination summary information - Passenger information, including occupation, gender, age category, ADA requirements and rate qualifiers NOTES: - For detail rail reservation information (including full itinerary details) for an exact match of a read request, the OTA_RailResRetrieveDetailRS message is typically returned. - Check with your trading partner to confirm their implementation of the Rail Read Reservation response messages.
OTA_RailScheduleRQ	The Rail Schedule Request message requests rail schedules for a city pair. Optional request information can include: departure time and flexible time windows and connecting cities. The flexibility of the message allows the request to be narrowed to schedules for a specific train.
OTA_RailScheduleRS	The Rail Schedule response message contains schedule information including origin and destination, equipment, marketing and operating companies, departure and arrival stations, accommodation and ancillary service information, etc.
OTA_RailShopRQ	The Rail Shop request message specifies search criteria for which rail pricing and availability should be searched for. Search criteria may include: - Information about the outbound (and optional return and connecting locations) between which availability and low fares available are to be checked - Passenger type(s) and category(s) - Global preferences for all origin and destination locations for both outbound and return trips (note that these preferences may be overridden elsewhere in the message) and include rail operator, transport modes, accommodations and amenities - Specific train number/ network code combination or just a network code - Rate qualifier(s) to specify the type of fares of interest to the traveler, along with any discount number or promotional codes that may affect the fare - Fare basis code(s) that apply to the whole trip Additional message functionality includes specifying detail point of sale information for the message initiator.
OTA_RailShopRS	The Rail Shop response message contains pricing and availability details for the requested search criteria, including origin/ destination location, accommodations and departure/ return dates and times. For each specified O/D pair, train options may be specified that include: - Origin/Destination location code and optional code context - Journey segment availability detail information, which may be for a train or a bus segment, and includes: * Specific inventory-controlled service class code or detailed accommodation information * Class and passenger type fares * Other service-related information including reservation class, reservation type, different class codes and auto train vehicle type Pricing details may be specified at the origin/ destination pair and/ or segment level, and include basic fare, alternate currency with exchange rate details, terms and conditions, adjustments, discounts, fees, taxes and ancillary charges. Developer Notes: » This message may also include Warnings from business processing rules or Errors if the request did not succeed.
OTA_ReadRQ	A generic message, available as an action on several OpenTravel services which requests a server to read and return the document type identified by the UniqueID element.
OTA_ResRetrieveRS	This message returns a list of reservations when an exact match on a read request could not be made or the request was to return a list of reservations meeting specified criteria.
OTA_Reviews	Comment describing your root element
OTA_ReviewsNotifRQ	Push message to send reviews for specified criteria.
OTA_ReviewsNotifRS	This message returns acknowledgement that the OTA_ReviewsNotifRQ has been successfully received, or includes warnings from business processing rules or errors if the request did not succeed.
OTA_ReviewsRQ	Pull message to request reviews for specified criteria with the ability to filter the response.
OTA_ReviewsRS	Response with reviews that matched specified criteria.
OTA_ScreenTextRQ	This message may be used to request information in a free text type of response using a terminal message input. It will allow users who do not have fully developed XML capabilities to send and receive XML messages and/or to request information for which there is no OpenTravel message functionality developed.
OTA_ScreenTextRS	The free text response to a screen text request. The responder may return a screen of information in a block of unformatted data or return a screen of information in a line by line response.
OTA_TourActivityAvailRQ	This message is used to request availability for a day tour and/or activity selected by the customer. Note that the tour and/or activity code is known to the availability system, e.g. a unique ID and/or name is being passed in the request in addition to date/ time, customer types and counts.
OTA_TourActivityAvailRS	This message provides the availability of a requested tour and/or activity. Alternate tour/ activity functionality is supported for tours/ activities that don't meet exact search criteria.
OTA_TourActivityBookRQ	A message to request a reservation for a tour and/or activity.
OTA_TourActivityBookRS	Information for the confirmation of a reserved tour/ activity.
OTA_TourActivityCancelRQ	A message to request a cancellation of a reservation for a tour and/or activity.
OTA_TourActivityCancelRS	This message acknowledges that the tour/ activity cancel message was received and processed successfully and/or has returned business warnings. If processed successfully, one or more Cancellation ID's will be returned with optional cancellation rules information and other details about the canceled reservation.
OTA_TourActivityModifyRQ	A message to request a modification to a confirmed reservation for a tour and/or activity. Note that the response to this message is an OTA_TourActivityBookRS message.
OTA_TourActivityResRetrieveRS	This message returns a list of tour/ activity reservation(s) information for two scenarios: The ReservationSummary element contains information for multiple reservations when an exact match on a read request could NOT be made. The ReservationDetail element contains detailed reservation information for one reservation that matched the reservation read request criteria.
OTA_TourActivitySearchRQ	This message allows a search for tours and/or activities matching specified criteria.
OTA_TourActivitySearchRS	This message provides tour and/or activities that meet the criteria in the Tour/Activity Search request.
OTA_TravelItineraryReadRQ	This message identifies the initial request for travel itinerary data.
OTA_TravelItineraryRS	This message is in response to a read RQ for a travel itinerary.
OTA_VehAvailRateRQ	OpenTravel vehicle rental availability message.
OTA_VehAvailRateRS	This element is the base element of the Vehicle Availability and Rates response message. The root element contains the standard payload attributes found in all OpenTravel payload documents.
OTA_VehCancelRQ	The root tag of the OTA_VehicleCancelRQ contains standard payload attributes found in all OpenTravel payload documents. The attribute ReqRespVersion is a positive integer value that indicates the version number requested for the response message.
OTA_VehCancelRS	The root tag of the OTA_VehCancelResRS contains the standard payload attributes found in all OpenTravel payload documents.
OTA_VehCheckInRQ	This message is used to collect information about the vehicle and equipment being returned.
OTA_VehCheckInRS	This message is used to return information about the vehicle and the equipment checked in.
OTA_VehCheckOutRQ	This message will allow a rental customer to engage in a car rental agreement allowing the customer to take possession of a specific vehicle.
OTA_VehCheckOutRS	This message provides rental agreement details (e.g., rate, surcharge, liabilities).
OTA_VehExchangeRQ	This message will allow a customer to exchange a vehicle that has already been checked out. The message accommodates the inclusion of information about the vehicle being exchanged as well as details of the vehicle being given in exchange.
OTA_VehExchangeRS	This message is used to return information about the vehicles involved in the exchange as well as a recap of the rate information.
OTA_VehLocDetailRQ	A Vehicle Location Detail request will allow car rental customers to request information about the car rental location. These are items that will assist the customer in basic information about the location.
OTA_VehLocDetailRS	Vehicle Location Detail response will allow car rental providers to return information about the location requested to assist the customer. This information includes address, phone number, informational messages, parking and counter location, services, and operating schedule of the location requested.
OTA_VehLocDetailsNotifRQ	This message will push location details for multiple car rental locations to a trading partner. The information pushed may establish this location initially in a trading partner's database and/or update the information that currently exists.
OTA_VehLocDetailsNotifRS	This message will acknowledge that the location details database update information has been received and successfully processed and may also specify a reference to a record that was not successfully processed.
OTA_VehLocSearchRQ	A Vehicle Location Search request allows car rental customers to request car rental provider(s) to return location(s) available. The search will be based on longitude/latitude of the location. Requests can be based on providing one or many of the following: longitude/latitude, address, telephone number, reference point, the actual code of the location, hotel, and/or radius.
OTA_VehLocSearchRS	Vehicle Location Search response will allow car rental customers to view location(s) available based on their request information. The response will include the OTA_VehLocSearchRQ information as well as physical address, telephone number, and additional information of the rental location(s) meeting their request. For example, a facility was identified based on a certain search criterion, and the facility is 10 miles away.
OTA_VehModifyRQ	The root tag of OTA_VehModiifyRQ contains standard payload attributes found in all OpenTravel payload documents. The attribute ReqRespVersion is a positive integer value that indicates the version number requested for the response message.
OTA_VehModifyRS	The root tag of OTA_VehModifyRS contains the standard payload attributes found in all OpenTravel payload documents.
OTA_VehRateNotifRQ	This message pushes rate details for car rental rates. The information pushed may establish this rate initially in a database and/or update the information that currently exists.
OTA_VehRateNotifRS	This message acknowledges that the OTA_VehRateNotifRQ has been received and provides information as to its processing result.
OTA_VehRateRuleNotifRQ	This message pushes rate rules. The information pushed may establish this rule initially in a database and/or update the information that currently exists.
OTA_VehRateRuleNotifRS	This message acknowledges that the OTA_VehRateRuleNotifRQ has been received and provides information as to its processing result.
OTA_VehRateRuleRQ	The OTA_VehRateRuleRQ will allow additional details to be requested regarding a previously quoted rate or a reservation that is already confirmed.
OTA_VehRateRuleRS	The OTA_VehRateRuleRS provides details regarding a previously quoted rate or a reservation that is already confirmed.
OTA_VehResNotifRQ	This message will push reservation details to a trading partner. The information pushed may establish this reservation initially in a trading partner's database and/or update the information that currently exists.
OTA_VehResNotifRS	This message acknowledges that the OTA_VehTransferNotifRQ has been received and provides information as to its processing result.
OTA_VehResRQ	The root tag of OTA_VehResRQ contains standard payload attributes found in all OpenTravel payload documents. The attribute ReqRespVersion is a positive integer value that indicates the version number requested for the response message.
OTA_VehResRS	The root tag of OTA_VehResRS contains the standard payload attributes found in all OpenTravel payload documents.
OTA_VehResStatusNotifRQ	Used to inform a trading partner of a confirmation or an update of an existing reservation.
OTA_VehResStatusNotifRS	Acknowledges that the status notif request has been received and provides information as to its processing result.
OTA_VehRetResRQ	The root tag of OTA_VehRetResRQ contains standard payload attributes found in all OpenTravel payload documents. The attribute ReqRespVersion is a positive integer value that indicates the version number requested for the response message.
OTA_VehRetResRS
VehReservation	Represents the vehicle rental reservation that was successfully created.

Index of Message Types