Live demo

Car rental supplier profile

Alamo Rent A Car API: supplier profile and how to connect

Alamo is a leisure car rental brand of Enterprise Mobility, strong at airport locations where holiday travellers pick up their cars. There is no self-service Alamo API for every agency, so this page explains how agencies usually reach Alamo cars and how PHPTRAVELS builds a custom connector into its cars module once you have the access.

  • An Enterprise Mobility brand
  • Three ways to reach the cars
  • Custom connector, built on request
  • Sold in the PHPTRAVELS cars module

Supplier fact sheet

Who Alamo is before you ask for access

Alamo opened in Florida in 1974 and built its name on leisure rentals: families and holiday travellers collecting a car at the airport. In 2007 the brand came under the same owner as Enterprise Rent-A-Car and National Car Rental, the group now known as Enterprise Mobility.

For an agency this matters in two ways. Commercial terms are usually agreed with the group rather than with one brand, and Alamo cars often reach the trade through channels you may already use, such as a GDS or a car rental aggregator.

Alamo Rent A Car
Brand
Alamo Rent A Car
Founded
1974, Florida, United States
Owner
Enterprise Mobility (Enterprise Holdings), since 2007
Sister brands
Enterprise Rent-A-Car, National Car Rental
Focus
Leisure rentals, mostly at airport locations
Trade channels
GDS car segments, aggregators, agent programmes
In PHPTRAVELS
Custom integration on request
Facts from public company information, checked October 2026.

Three routes

How agencies reach Alamo cars

Pick the route that matches the contracts you already hold. Each one ends in the same place: Alamo cars on your site and agent portal, next to the other car suppliers you sell.

  1. 01

    Through a GDS

    What you need
    A GDS agreement that includes car rental, with Alamo cars available in your markets
    What PHPTRAVELS does
    Adds the car segment calls to your GDS connection and maps the results into the cars module
    Best for
    Agencies already booking flights through Sabre, Amadeus or Travelport
  2. 02

    Through a car aggregator

    What you need
    An aggregator contract whose supply includes Alamo in the countries you sell
    What PHPTRAVELS does
    Uses a car supplier already in the cars module, or connects your aggregator as custom work
    Best for
    OTAs that want many rental brands through one contract
  3. 03

    Direct with the group

    What you need
    A commercial agreement with Enterprise Mobility and the technical access it issues
    What PHPTRAVELS does
    Builds a dedicated connector around the specification and credentials you receive
    Best for
    Large or specialised sellers with their own negotiated rates
Cars & transfersWhich brands and locations each channel carries depends on your contract and market. Ask your GDS or aggregator account manager before you plan the build.
Car resultsOrlando airport (MCO) · 5 days
  • ECAREconomyAlamoAirport counterUnlimited mileageAutomaticPay now$38 per dayTotal $190Select
  • CCARCompactAlamoAirport counterUnlimited mileageAutomaticFree cancellation$42 per dayTotal $211Select
  • ICARIntermediateAlamoAirport counterUnlimited mileagePay at counter$51 per dayTotal $255Select
  • IFARIntermediate SUVAlamoAirport counterUnlimited mileageAutomaticFree cancellation$67 per dayTotal $336Select

Sample data to show the layout. Not live Alamo rates.

What your customers see

An Alamo quote inside the cars module

Whatever the route, the connector turns the supplier response into the same results card as every other car supplier, so customers compare like for like.

What the module adds to every quote

  • Vehicle classes kept as standard four-letter codes, so filters work across suppliers
  • Base rate, taxes and fees shown as one total with the breakdown one click away
  • Driver age, deposit and cancellation rules shown before the customer pays
  • Your markup and agent commission applied per channel

Field mapping

What we map from Alamo to your booking engine

Most of a car integration is careful mapping. These are the fields we agree with you in the scope, whichever route you use.

Supplier dataPick-up and return locations, airport codes, opening hours
Where it lands in PHPTRAVELSLocation search and the opening-hours check on the search form
Supplier dataVehicle class code, transmission, doors, seats, bags
Where it lands in PHPTRAVELSCar card, class filters and the comparison view
Supplier dataBase rate, included mileage, taxes and local fees
Where it lands in PHPTRAVELSOne total price with a line-by-line breakdown
Supplier dataChild seats, extra driver, navigation, protection products
Where it lands in PHPTRAVELSAdd-ons on the checkout page, priced per day or per rental
Supplier dataMinimum age, young driver fees, licence rules
Where it lands in PHPTRAVELSDriver details step and the rules shown before payment
Supplier dataPrepaid or pay at the counter, deposit rules
Where it lands in PHPTRAVELSCheckout options and the voucher text
Supplier dataCancellation and no-show terms
Where it lands in PHPTRAVELSPolicy line on the card, the voucher and the cancel flow in My bookings

Custom integration

From access to your first Alamo booking

A custom connector follows five steps. Each step ends with something you can check, so you always know where the project stands.

How custom integrations work

  1. 01

    Scope the route

    We confirm which route you use, which countries and airports you sell and which car classes matter.

    You getA written scope and a fixed quote

  2. 02

    Get the access

    You obtain test credentials and the technical documents from your GDS, aggregator or Enterprise Mobility contact.

    You getA working test account

  3. 03

    Map and build

    We build search, rules, booking and cancellation against the test system and map every field into the cars module.

    You getAlamo results on a staging site

  4. 04

    Test real cases

    Airport and city pick-ups, one-way rentals, young drivers, extras and cancellations are booked and checked end to end.

    You getA signed-off test log

  5. 05

    Go live

    Production credentials are switched on, markups are set per channel and the first bookings are watched closely.

    You getAlamo cars on sale

Car suppliers already in the cars module

These car suppliers are connected in PHPTRAVELS today. Some sell several rental brands, so ask them whether Alamo is in their supply for your markets before you plan a separate build.

See alsoCarTrawler API integrationCar rental systemGDS system for travel agents

  • KiwiTaxi
  • CarTrawler
  • Discover Cars
  • Mozio

FAQ

Questions about the Alamo Rent A Car API

What agencies usually ask before they add Alamo cars.

Talk to sales

Not as a self-service product for every agency. Access normally comes through a GDS, a car rental aggregator or a commercial agreement with Enterprise Mobility, and the technical access depends on that contract.

No. Alamo is not in the list of car suppliers PHPTRAVELS connects out of the box. We build the connection as a custom integration once you have access through one of the three routes.

Often the same agreement or channel covers the group's other brands, but that depends on your contract. If it does, the same connector can show all the brands you are allowed to sell.

It depends on the route and the documentation you receive. We give a fixed scope and timeline after reviewing the access and the documents, before any work starts.

Yes. The cars module serves your public website and your agent portal, with separate markups and commissions for each channel.

Yes, once the connector is live every search asks the supplier channel for current availability and prices. The figures on this page are only sample data to show the layout.