Requesting Additional Results (Get More)

For some providers, if additional responses data is available after the first response, one or more follow-on transactions can be made to return additional availabilities.

Additional Results for Air, Vehicle, Rail, Queue, and Hotel Search Responses

NextResultReference is available for air, vehicle, rail, and queue responses, as well as Hotel Search and Hotel Rate and Rule Search responses.

If additional data is available, the first response returns a key in the NextResultReference element. This key is sent, with the applicable provider code, in the following request to indicate the starting point of the second group of responses. Subsequent keys can be used for each additional transaction in the request.

If no key is returned in a NextResultReference response, no additional search responses are available.

Additional Results for Hotel Super Shopper Responses

Requests for additional properties are not currently supported in Hotel Super Shopper. The NextResultReference token is not currently functional in HotelSuperShopperReq and HotelSuperShopperRsp.

However, requests for additional rates are supported for Hotel Super Shopper. By default, a maximum of 99 rates plans are returned for each hotel property.

If additional rate plans are available for a property, a More Rate indicator is returned (HotelProperty @MoreRates=”true”). An associated More Rates token (HotelProperty @MoreRatesToken) can be used in a subsequent Hotel Rate and Rule Search request for a specified property (HotelDetailsReq/NextResultReference).

@MoreRatesToken is present, but not implemented in HotelProperty for:

Note: QuickResponse @MoreToken is also not currently supported, and is reserved for future use.

Exceptions

Galileo supports requesting additional results.

Apollo supports requesting additional results.

Worldspan does not support requesting additional results.