Overview
This article provides a comprehensive guide to Nezasa's Alamo connector, with insights into its use cases. Alamo Rent-A-Car is a prominent car rental company based in the United States, known for its affordable and convenient car rental services, primarily catering to leisure travellers.
With Alamo as a provider, users can access a wide selection of vehicles, including economy cars, SUVs, minivans, and more. Nezasa's TripBuilder has seamlessly integrated an Alamo connector, enabling access to car rental offers.
Integrating with Alamo brings together three prominent rental car suppliers: Alamo, Enterprise, and National. These suppliers are part of the same company, Enterprise Holdings Inc., which enables them to collaborate closely and share resources. Alamo is a technological switch that facilitates seamless coordination between the brands, allowing users to access and compare rental car offers on a single platform. This collaboration enhances the service by offering users a broader range of choices, including different geographic coverage, rental car products, and terms and conditions. The integrated approach aims to enhance the overall rental car experience by offering convenience and a comprehensive selection of options.
Supported Use Cases
Use Case | Support Description |
Search Offers | Supported |
Get Offer Details | Supported |
Availability Check | Supported |
Book | Supported |
Cancel | Supported |
Booking Change |
Not supported (a cancel/re-book is needed) |
Name Change |
Not supported (a cancel/re-book is needed) |
Reconciliation / Webhooks | Not Supported |
Cancellation Policies via API | Not Supported |
Pick-Up / Drop-Off City (not Airport) |
Supported |
Setting up new credentials
Setting up Alamo’s credentials requires information from the supplier, namely:
- Company Short Name
- Company Name Code
- Username
- Password
- Contract specification, the alphanumeric characters are generally in uppercase, but there's no specific fixed format. Customers will receive a list categorised by market (USA, CA) and suppliers (ALAMO, ENTERPRISE, NATIONAL).
Suppose you have contractually agreed with Alamo only to distribute APAC products for Alamo and National vendors. In that case, specific codes for each country to be distributed in the APAC region per Vendor are required.
Example
Country | Alamo | National |
Australia | NZXXX01 | NZYYY01 |
New Zealand | NZXXX01 | NZYYY01 |
Japan | NZXXX01 | NZYYY01 |
Guam | NZXXX01 | NZYYY01 |
Palau | NZXXX01 | NZYYY01 |
Philippines | NZXXX01 | NZYYY01 |
Saipan | NZXXX01 | NZYYY01 |
Please contact our support team or your customer success manager for more info or consult your Alamo pier.
Certification
Please be aware that Alamo requires a credential certification for every new customer connection.
After the commercial agreement is finalised between the customer and Alamo, the Nezasa onboarding team will request testing credentials from Alamo and begin the staging certification process. The process of requesting credentials, setting up connections, retrieving and validating logs usually takes 10-15 working days, involving both Nezasa and Alamo technical teams.
Upon successful certification in the staging environment, Alamo will provide production credentials to Nezasa. The same process is followed for the staging certification, taking approximately ten working days on average. Once production certification is achieved, Nezasa will contact the customer, seeking clearance to activate the Alamo connection live.
Special Equipment / Costs in Destinations
Inclusions and exclusions of special equipment and costs are configured with your credentials by the Alamo IT departments. These conditions are based on your negotiated rate plan. Make sure to check these details with your Alamo customer success manager.
Cancellation Policies
Cancellation policies are not shared via the API. Nezasa must manually configure your contracted conditions when setting up your credentials. Please share the cancellation policy details and if they are generic or specific by country/vendor.
Testing
To get started with the Alamo connector in a testing environment, it’s essential to be aware of the correct endpoint in use. Nezasa’s technical team conducts this validation. The testing instance is used at the first stage between Nezasa and Alamo to support the certification process that needs to take place for each new customer. Once complete, additional test bookings can take place. Please always cancel them, even considering the testing/staging environment.
Alamo specifics
Residency Requirements for Driver
During the itinerary planning, the Alamo Connector makes it mandatory to pre-define the Driver residency country before getting rental car results. Different offers (vehicle, conditions and/or pricing) can be presented depending on the Driver residency country.
Since traveller details (including the driver) are only collected at checkout, in the Rent a car search page, both the Driver age and Driver residency need to be pre-defined at this stage.
Going forward, when reaching the Checkout, both parameters will be compared with the data entered by the user to ensure consistency and correctness.
Please note: Driver residency is different from Nationality. A rental car driver can have French nationality and residency in Italy, for example. |
Address Requirements for Driver
In Checkout, and for the traveller that is defined as Driver, besides the country of residence that's fixed to the selection conducted at the rental car search and cannot be changed, further information on the driver's address is required:
- Address Line 1*
- Address Line 2
- Postal Code*
- City*
- Country*
(*) Mandatory field
Vouchers
Alamo doesn't provide vouchers directly. Instead, TripBuilder has a generic voucher feature that provides vouchers in case of Alamo bookings. Please see the usual voucher section in Customer Care.
Comments
0 comments
Article is closed for comments.