Sessions: Booking Air Segments

Booking Air Segment requests enable the addition of Air Segments to the transient PNR.

• Connections will be sold together.
• Universal API returns the same error as is returned from the provider on failure to sell air segments.

Samples

See the samples associated with Booking Air Segment.

• Request
• Response

Schema

See the Booking Air Segment transactions:

Standard Air Segment Add

• BookingAirSegmentReq
• BookingAirSegmentRsp

Book a segment without adding traveler names first using @NumberInParty

• AddAirSegment_NumberInParty_Req

• AddAirSegment_NumberInParty_Rsp

Request

When booking an Air Segment in a sessioned state, the element and attribute structure is similar to the request in a standard Air Booking or Modify request, except that a session must have been established (Booking Start), and a session key must be sent in the header and body of the request.

 

 

Number in Party

The number in party must be specified in the request unless all Booking Travelers have already been added to the session.

 

Add Air Segment / Update Segment / Delete Segment

The rules that apply for Universal Record Modify also apply to Add, Update, and Delete Air Segment.

Only 3 options can be updated in the segment:

• Segment Status.
• Class of Service.
• Date and Time of Flight.

The following items apply to these elements:

• Air Segment Reference is mandatory in the request for the update and delete.
• Delete segment requests delete the air segment based on the reference.
• Cancellation of flight segments may result in cancellation of PNR elements like SSRs, Stored Fares, etc.

Response

The Booking Air Segment Response returns a universal record structure with all details for the current state of the session.

Exceptions

The exceptions for Booking Air Segment element is mostly the same as can be found in Air Create or Air Modify, unless any listed below: