Sessions: Booking PNR Elements

The Booking PNR Element Request enables the addition, deletion, and modification of the following elements. All the existing Universal API validations stay and validation errors are the same as Air Create Reservation Request errors.

• PNR level Form of Payment
• Action Status
• General Remarks
• Unassociated Remarks
• Accounting Remarks
• OSI (Other Supplementary Information)

Samples

See the samples associated with Session Air Workflow.

Note: All actions listed in the introduction can be combined in a single request.

Schema

Refer to the SharedBooking schema.

See the Booking PNR Element transactions:

• BookingPnrElementReq
• BookingPnrElementRsp

Request

When adding a PNR Element 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.

Prior to Universal API Release 21.1.1, when in a session, Universal API customers needed to send three separate requests: Ticket information, Other Service Information (OSI), and then Form Of Payment (FOP) information, which incurred significant latency with each transaction due to network overhead. The enhancement with Release 21.1.1 allows Ticket, OSI, and FOP information in a single BookingPnrElement request. Release 21.1

 

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 End are the same as can be found in Air Create or Air Modify. There are no known exceptions specific to the Booking PNR Element transaction.