Emailing Itineraries

Travelport Universal API supports emailing itinerary confirmations to travelers and/or agencies after booking for certain providers and travel segment types.

Note: Individual suppliers and may also send itinerary confirmations; however, this functionality is not regulated by Universal API.

Implementation by Provider

See Implemented Transactions for provider functionality specific to each transaction.

Provider

Implementation
Galileo (1G) Itineraries can be emailed for Air, Hotel, and Vehicle Bookings.
Apollo (1V) Itineraries can be emailed for Air, Hotel, and Vehicle Bookings
Worldspan (1P)

Itineraries are emailed to all travelers for Air, Hotel, and Vehicle Bookings.
Airline Content Hub (ACH) Itinerary confirmations from providers are not supported by ACH for Air reservations. However, individual ACH suppliers may send itinerary information.
Rail Content Service (RCS) Itinerary confirmations from providers are not supported for Rail reservations. However, individual RCS suppliers may send itinerary information.

How To

Galileo and Apollo use the EmailNotification element to specify the recipients of itinerary confirmation emails.

By default, Worldspan emails itineraries to all travelers with email addresses listed in the booking (PNR).

Email distribution is automatic; no input is required from the client application. This functionality applies to Air Booking, Hotel Booking, and Vehicle Booking.

Schema

For Galileo (1G) and Apollo (1V), the EmailNotification element is used to specify the type of email notification in the Booking request (*CreateReservationReq).

 

Element/Attribute Description
EmailNotification Supported by Galileo (1G) and Apollo (1V) to email itinerary confirmations to booking travelers.
@Recipients

Galileo and Apollo use an Email Notification functionality which permits itinerary confirmations to be emailed.

  • EmailNotification @Recipients="All"
    All travelers in the itinerary.
  • EmailNotification @Recipients="Specific"
    Specified travelers in the itinerary.
  • EmailNotification @Recipients="Default"
    The default email address is the first email address of the first (primary) booking traveler at the time of creation of the PNR. If the first traveler does not have an email address, then the next available email address of the consecutive traveler at the time the booking (PNR) is created is used as the default email address.
EmailRef If EmailNotification @Recipients="Specific", EmailRef keys can be used to indicate which Booking Traveler email addresses are sent for itinerary confirmations.

Implemented Transactions

AirCreateReservationReq (default in Worldspan)

AirCreateReservationReq/EmailNotification (Galileo and Apollo)

Supported for Worldspan (1P), Galileo (1G), and Apollo (1V).

Individual ACH suppliers may send confirmations directly to the traveler.

HotelCreateReservationReq (default in Worldspan)

HotelCreateReservationReq/EmailNotification (Galileo and Apollo)

Supported for Worldspan (1P), Galileo (1G), and Apollo (1V).

VehicleCreateReservationReq (default in Worldspan)

VehicleCreateReservationReq/EmailNotification (Galileo and Apollo)

Supported for Worldspan (1P), Galileo (1G), and Apollo (1V).

RailCreateReservationReq

Itinerary confirmations from providers are not supported for Rail reservations. However, individual suppliers may send itinerary information for Rail Bookings.

The EmailNotification element is present in RailCreateReservationReq, but is not supported for Galileo (1G) or Apollo (1V).

PassiveCreateReservationReq

Itinerary confirmations are not supported for Passive Bookings.

The EmailNotification element is present in PassiveCreateReservationReq, but is not supported for Galileo (1G) or Apollo (1V).