dc-core /pnr

Digital Connect gives the airlines an ability to present offers to passengers, who can choose among the listed offers for itinerary, fill in the passenger details, select ancillaries, seats, and order the purchased items. 

  

Using the Digital Connect Service Suite - Shopping 

To make use of the services and book flights (simple booking scenario), use the services in the following order: 

Search Flight (Required) 

This API empowers the airline to help passengers book Flights based on their criteria like origin, destination, dates, Type of Journey (OneWay, RoundTrip, MultiCity), number of passengers and type of passengers and providing support for any promotional codes.  

The API responds with list of flights matching the search criteria having flight/itinerary details and price information (Base, Taxes, Total) and each flight is referenced with ShoppingBasketHashCode. 

Select Flight (Required) 

Once the passenger selects the flight, the API will assist the airline to add the selected flight/flights to the cart/session for All Journey types - OneWay, RoundTrip, MultiCity. Airline inputs flight Offers using the reference (shopping basket hash code) from Search Flight Response. 

The API responds with selected flight details confirming the flight selected. 

Add Passenger Details (Required) 

This API allows passengers to add passenger details like Name details (Prefix, First Name, Last Name, Middle Name, Suffix), Contact Details (Email, Phone, Address), Preferences ( Meals, Seats, Special Service Requests), Add Frequent Flyer and Other passenger information (e.g. Passport, Visa, National ID). 

The API response will confirm all the passenger details to the session. 

• Submit a POST /passengers request to add passengers to an itinerary. You can also use POST to update, by submitting all of the passenger data including the updated fields, and to delete passengers from the itinerary, by submitting all of the passenger data, including blank fields for the deleted passengers. 

• Submit a GET /passengers request to display the current passenger data for the itinerary. 

Add Ancillaries (Optional)

After an itinerary and passenger details have been stored in the session, use /products/ancillaries operations to show passengers the ancillaries available on the flights they have selected and to add any ancillaries selected by the passenger to the itinerary.   

• Submit a GET /products/ancillaries request to obtain a list of ancillaries available for the flights in the itinerary, based on the information available in the session /products/ancillaries will display these ancillaries to the passenger for selection. 

• The GET /products/ancillaries response returns with list of ancillaries available for the itinerary and applicable passengers with pricing information. 

• Submit a POST /products/ancillaries request to add ancillaries to the itinerary. You can also use POST to update, by submitting all of the ancillary data including the updated fields, and to delete ancillaries from the itinerary, by submitting all of the ancillary data, including blank fields for the deleted ancillaries. 

• The POST /products/ancillaries response returns with list of ancillaries added to the session with ancillary, passenger and segment details. 

Add Seats (Optional) 

After adding all the offers to the session, use /products/seats operations to show passengers the seats available on the flights,  based on the information available in the session /products/seats will expose seat maps and add any available seat selected by the passenger.   

• Submit a GET /products/seats request to the information used to construct seat maps for the flights in the itinerary. The seat information will indicate available seats and reserved seats, free seats and paid seats, and so on. Use this information to format a seat map for display to the passenger for selection. 

• The GET /products/ancillaries response returns with list of seat maps based on the passengers in the sessions for the itinerary and applicable passengers with pricing information and seat characteristics, limitations, facilities, seat number, location, and more. 

• Submit a POST /products/seats request to add seats to the itinerary. You can also use POST to update, by submitting all of the seat data including the updated fields, and to delete seats from the itinerary, by submitting all of the seat data, including blank fields for the deleted seats. 

• The POST /products/seats response will confirm the seat status with segment and passenger details. 

Shopping Cart (Optional) 

At any time after an itinerary has been stored in the session, use a GET /products operation to obtain a current list of products that the passenger has added to the session/itinerary along with their prices. Use this information to build and display a shopping cart.

The GET /products service responds with itinerary information, passenger details, total amount for products selected by the passenger, and price information of each product with price breakdown (Base, Taxes, Total, Surcharge-if any applicable). 

Payment Options (required) 

After the passenger has completed building the itinerary in the session, including ancillaries and seats use /paymentOptions to retrieve available FOPs . 

• Submit a GET /paymentOptions request to obtain a list of available forms of payment (FOP) and amounts (surcharges included). You can display these forms of payment to the passenger for selection. 

• The GET /paymentOptions will respond with all the available Forms Of Payments (Credit Cards/Debit Cards, Additional Forms of Payments, installments and more, Also information with surcharges and Combinational Forms of payment if the passenger wants to pay with 2 Forms of payments. 

• Submit a POST /paymentOptions request to send FOP code with amount to get in the response a list with all combinable forms of payment with amount (residual amount). 

• The POST /paymentOptions responds with Additional Options for the selected payment method, Example if a credit card is availed with installment options with installment plan details. 

Purchase (Required) 

After the passenger has completed building the itinerary in the session, including ancillaries and seats, collect payment data from the passenger and submit using the /purchase request.  

The /purchase request will submit billing data to the FOPs supplied by the passenger and, if payment is authorized,  then purchase service creates a PNR adding details during the session. 

The POST /purchase response contains details of the PNR.