Skip to main content

dc-core

Air
Search
REST API
Airline Carrier
Try Now

What is it?

Revenue Flow (B2C)

This group of services provides functionality that enables an airline to present offers and give the passenger the possibility to build an itinerary and book the itinerary.

Redemption Flow (RBE)

The Frequent Traveler Award Redemption function allows frequent travelers to access their mileage balance and redeem those miles for points they can use during purchase. Digital Connect retrieves passengers profile with the available points. The paymentOptions/details/AWARD Service provides the minimum and maximum quantity of points to pay for a flight. It also returns possible combinations of points and currency, which the client may use in Multiple Forms of Payment.

How it works

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 step):

Obtain search criteria from the passenger and submit a /products/air/search request, POST operation to get a list of flights matching the search criteria. Display the returned flights to the passenger. This request will create a session. From the response, collect the execution ID, JSESSIONID cookie, WLPCOOKIE cookie, and SSWGID cookie, which you will use in subsequent requests to maintain the session.The response also includes a ShoppingBasketHashCode for each flight.

Select Flight (required step):

After the passenger selects one or more flights, use the /products/air POST operation to add the flights to the itinerary and store the itinerary in the session. The request must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID cookie from the search response to maintain the session. Use the hash codes for the passenger-selected flights to identify the flights in the POST operation. Use the GET operation to retrieve the itinerary, or additional POST operations to update the itinerary. Omitting the execution ID from these operations will lead to an error.

Shopping Cart (optional step):

At any time after an itinerary has been stored in the session, use a /products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary. Use this information to build and display a shopping cart. You will probably build and display a shopping cart on every page of your user interface.

The request must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID cookie from the original search response to maintain the session. Note that you can submit a /products GET request at any time after the first /products/air POST request has created an itinerary in the user session.

Add Passenger Details (required step):

After an itinerary has been stored in the session, use /passengers operations to add passengers to the itinerary. Requests must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID cookie from the original search response to maintain the session.

Submit a /passengers POST 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 /passengers GET request to display the current passenger data for the itinerary. Add Ancillaries (optional):

After an itinerary has 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. Requests must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID from the original search response to maintain the session.

Submit a /products/ancillaries GET request to obtain a list of ancillaries available for the flights in the itinerary. You can display these ancillaries to the passenger for selection. Submit a /products/ancillaries POST 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.

Add Seats (optional step):

After an itinerary has been stored in the session, use /products/seats operations to show passengers the seats available on the flights they have selected and to add any seats selected by the passenger to the itinerary. Requests must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID from the original search request to maintain the session.

Submit a /products/seats GET request to the information used to construct seat maps for the flights in the itinerary. The seat information will indicate available and reserved seats, free and paid seats. You can use this information to format a seat map for display to the passenger for selection. Submit a /products/seats POST 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.

Payment Options (required step):

After the passenger has completed building the itinerary in the session, including ancillaries and seats use /paymentOptions to retrieve available FOPs .The requests must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID from the original search request to maintain the session.

Submit a /paymentOptions GET 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. Submit a /paymentOptions POST request to send FOP code with amount to get in the response a list with all combinable forms of payment with amount (residual amount).

Purchase (required step):

After the passenger has completed building the itinerary in the session, including ancillaries and seats, collect payment data from the passenger and submit a /purchase request. The request must include the header data, execution ID, JSESSIONID cookie, WLPCOOKIE cookie and SSWGID from the original search response to maintain the session.

The /purchase request will submit billing data to the FOPs supplied by the passenger and, if payment is authorized, create a PNR.

Payment Options AWARD API

After selecting their seats, the passenger can switch to points to be able to pay for the booking or part of the booking using the Award Form of Payment. During the switch, a reprice of the current reservation is performed and product breakdown in points is returned. To be able to switch to points, the passenger needs to be logged in and have sufficient points balance. If after switching to points the passenger makes any changes to their reservations, the reservation is automatically switched back to cash. The passenger needs to switch to points again to reprice the updated reservation to points.