Booking Guide for Failed/Shell Bookings

This guide details the functionality supported for shell bookings, which is a reservation that does not have any air segments booked and contains only traveler details.

Shell bookings are supported only for GDS, not NDC.

Related Content: Booking Guide, Reservation Retrieve Guide, Reservation Retrieve API Reference

In this topic:

Basic Concepts

In the case of bookings that fail due to inability to either add the offer or quote a fare, if the autoDeleteDate query parameter is sent at commit, AirReservation creates a reservation shell that retains the traveler details. This allows an agency to contact the customer offline through their call center and complete the booking as necessary, or to retrieve the reservation and complete the booking later with the usual JSON API booking workflow.

Setting Up a Reservation Shell in Case of Booking Failure

In the initial booking workflow, you can ensure a shell booking is created in the event there is a booking failure either because the offer cannot be added or the fare cannot be quoted. To do so, include the autoDeleteDate query parameter in the workbench commit at the end of the initial booking workflow.

Ticketing a Shell Reservation

You can ticket a failed booking with a reservation shell using the following workflow:

  1. Create a post-commit workbench request, sending the locator code for the failed booking.

  2. Send an Add Offer request.

  3. If necessary, send an Add Traveler request to complete traveler details.

  4. Send an Add Form of Payment request.

  5. Send an Add Payment request.

  6. Send a Commit Workbench request.

Optional steps such as seats, ancillaries, or remarks are also supported in the workflow above after adding the offer and traveler/s.

Adding or Deleting Remarks

You can add and delete the following types of remarks to a shell booking. These remarks are returned in the Reservation Retrieve response:

  • Vendor remarks

  • DOCI remarks

  • Itinerary (associated and unassociated) remarks

  • Notepad remarks

  • Historical Notepad remarks

  • Accounting remarks

  • OSI remarks

To add and delete remarks, use the applicable workflow in the Remarks and Service Requests Guide.

Updating Traveler Details

You can add, update, and delete any traveler details supported in the TravelerUpdateableItems request. See the Traveler Modify Guide.

Examples

The following example reservation retrieve response returns a reservation shell for a failed booking. Note that no offer details are returned, and the Result object returns the warning NO FARES FOUND.