Vehicle Search with Loyalty Program
A Vehicle Search request can be modified to include a supplier's Loyalty Program (Frequent Traveler) membership ID.
Request
In addition to the minimum required data for a Vehicle Search, the car type options are added as attributes of the VehicleSearchAvailabilityRequest/VehicleSearchModifiers/LoyaltyCard.
The following attributes are required for the request:
- SupplierCode, which is the car supplier's ID.
- CardNumber, which is the traveler's Loyalty Program membership ID with the corresponding supplier.
Because travelers may earn credit for a car rental using the car rental company's Loyalty program and/or an air carrier's Loyalty program, SupplierType is used to indicate if the traveler's loyalty membership is affiliated with an Air suppler or a Car supplier.
Universal API supports up to three Corporate Discounts per supplier and one Loyalty Card per supplier when RateModifiers/RateCode is not specified. When a rate code is specified, only one supplier is allowed; therefore, only one Corporate Discount and one Loyalty Card is allowed per transaction.
Response
The response returns the available options for a Vehicle Search. The supplier may return rental rates that are modified based on a Loyalty Membership incentive.
Exceptions
Worldspan
Worldspan does not support:
- Individual traveler's Loyalty Program membership ID. However, a request can be made using the vehicle supplier's Customer ID when a specific supplier is also requested.
- Cross-accrual with Air, Hotel, or other supplier loyalty cards; only Car supplier loyalty cards are recognized.
- PermittedVendors and ProhibitedVendors with multiple Loyalty Cards.
One to three Customer IDs can be sent in a single call. The supplier code is required for each ID number when multiple IDs are sent.
VendorLocationRef is Worldspan (1P) only:
- The Vendor Location Reference associates of the RateModifiers (and LoyaltyCard) information to the correct Pickup and Return Locations.
-
If VendorLocationRef is in the request, the /VendorLocation@Key is required with the same value.
- When the VendorLocationRef is present and there is no VendorLocation/@key of the same value, Universal API returns the following error: “Match VendorLocation/@Key to veh:VendorLocationRef and resend request”
-
When more than one Pickup Location is requested and the VendorLocation/@Key is not present and/or a VendorLocationRef is not present with a RateModifier or LoyaltyCard, Universal API returns the following error: “Missing VendorLocation/@Key or veh:VendorLocationRef, update and resend request.”