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 can create a reservation shell that contains 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.

AirReservation 23.11.29 added several additional features per below.

Creating a Reservation Shell in case of Booking Failure

In the initial booking workflow, to ensure that AirReservation retains traveler details if the booking fails either because the offer cannot be added or the fare cannot be quoted, send the autoDeleteDate query parameter with any value at the workbench commit to create a reservation shell.

Ticketing a Shell Reservation

AirReservation 23.11.29 and later.

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

  1. Create Post-Commit Workbench request sending the locator code for the failed booking.

  2. Add Offer request.

  3. Add Traveler request if necessary to complete traveler details.

  4. Add Form of Payment request.

  5. Add Payment request.

  6. 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

AirReservation 23.11.29 and later.

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 Comments and Service Requests Guide.

Updating Traveler Details

AirReservation 23.11.32 and later.

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.