Hotel Name Autocomplete

Name: Hotel Name Autocomplete API
Brand: Hotel Name Autocomplete
Availability: InStock

✓ Official Vendor SpecMaps GeolocationPlaces Searchoauth21 EndpointsREST

For Agents

Resolve partial hotel or destination keywords into structured Amadeus location records, including hotel IDs and city codes that can be passed to Hotel Search or Hotel Booking calls.

Quickstart

Get started with Hotel Name Autocomplete in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"autocomplete a hotel name"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Hotel Name Autocomplete API.

Resolve a partial hotel name into matching Amadeus hotel records with hotelIds for downstream pricing calls

Surface city and airport matches alongside hotels so a single search box covers destinations and properties

Filter autocomplete results by sub-type (HOTEL_LEISURE, HOTEL_GDS, etc.) to scope suggestions to a specific inventory

Return IATA city codes and geocoordinates to seed a hotel-offers query in test.api.amadeus.com/v1

GET STARTED

Start building with Hotel Name Autocomplete API

Explore with Jentic

View OpenAPI Document

The Amadeus Hotel Name Autocomplete API returns matching hotels and destinations from a partial keyword, helping booking interfaces and travel agents surface suggestions as a user types. It searches hotel names, chains, cities, and airports across the Amadeus reference data set and returns the IATA code, geographic coordinates, and hotel identifiers needed to feed downstream search calls. The single endpoint is built for low-latency typeahead use, with configurable result counts and category filters for hotels, locations, or both.

Use Cases

Patterns agents use Hotel Name Autocomplete API for, with concrete tasks.

★ Booking-flow typeahead suggestions

Power the search bar of a hotel booking site with live suggestions as the traveller types. The API returns matching hotels and destinations in milliseconds, including the hotelId and IATA city code needed to populate the next step of the funnel. Implementation is a single GET call against /reference-data/locations/hotel and slots into any debounced input handler.

Call GET /reference-data/locations/hotel with keyword=PARI and subType=HOTEL_LEISURE, then return the top 5 hotelIds and city codes.

Hotel ID resolution before pricing

Translate a free-text hotel reference (a name in a CRM record, a row in a spreadsheet) into the structured Amadeus hotelId required by Hotel Search and Hotel Booking. The autocomplete endpoint accepts the keyword and returns canonical identifiers, eliminating the need to maintain a local hotel-name-to-id map. Useful for migrations, bulk re-pricing, and reconciling third-party data with Amadeus inventory.

Given the string 'Hilton London Paddington', call the autocomplete endpoint and return the hotelId from the first HOTEL_GDS-subtype result.

Multi-entity destination search

Build a unified destination search where a single query returns cities, airports, and hotels in one ranked list. The API supports a subType parameter that allows HOTEL_LEISURE, HOTEL_GDS, and location entities to be requested together so the UI does not need separate calls for each entity type. Results include category and geocode so the front-end can render appropriate icons and zoom states.

Search for keyword='new' and return a deduplicated list of matching cities, airports, and hotels with their type labels.

AI agent travel concierge

An AI agent helping a user plan a trip uses the autocomplete endpoint to disambiguate hotel and city references in natural-language input. When the user says 'find me a Marriott in Berlin', the agent calls Jentic to discover the Hotel Name Autocomplete operation, resolves 'Marriott' and 'Berlin' to structured ids, then chains into Hotel Search for live availability. Total integration via Jentic is under an hour.

Use Jentic to search 'autocomplete a hotel name', load the Hotel Name Autocomplete schema, and execute it with keyword='marriott' subType='HOTEL_LEISURE'.

Key Endpoints

1 endpoints — the amadeus hotel name autocomplete api returns matching hotels and destinations from a partial keyword, helping booking interfaces and travel agents surface suggestions as a user types.

METHOD

PATH

DESCRIPTION

GET

/reference-data/locations/hotel

Return hotels and destinations matching a keyword

GET

/reference-data/locations/hotel

Return hotels and destinations matching a keyword

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Amadeus OAuth2 client_id and client_secret are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execution time; the long-lived client secret is never exposed to the agent or LLM context.

Intent-based discovery

Agents search by intent ('autocomplete a hotel name') and Jentic returns the Hotel Name Autocomplete operation with its keyword, subType, and countryCode parameters, so the agent can call it without browsing the Amadeus self-service docs.

Time to first call

Direct Amadeus integration: 1-2 days for OAuth handling, token refresh, and error mapping. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amadeus Hotel Search

Use Hotel Search after autocomplete to retrieve live offers and pricing for the selected hotelId.

Choose Hotel Search once the user has selected a specific hotel suggestion and you need rates, room types, and offer IDs.

Complementary

Amadeus Hotel Ratings

Pair autocomplete with Hotel Ratings to enrich suggestions with traveller sentiment scores.

Choose Hotel Ratings when the agent needs to surface review-based quality signals alongside autocomplete results.

Complementary

Amadeus Hotel Booking

Hotel Booking is the downstream call that turns a chosen hotel offer into a confirmed reservation.

Choose Hotel Booking after autocomplete and Hotel Search have produced an offerId the user wants to book.

FAQs

Specific to using Hotel Name Autocomplete API through Jentic.

What authentication does the Hotel Name Autocomplete API use?

The API uses OAuth 2.0 client credentials. You exchange your Amadeus API key and secret for a bearer access token via the Amadeus authorization endpoint, then send it as the Authorization header on each call. Through Jentic, your Amadeus credentials stay in the Jentic vault and the agent only ever sees a scoped token, so the raw client secret never enters the agent's context.

Can I look up a hotel by partial name with this API?

Yes. The single endpoint GET /reference-data/locations/hotel accepts a keyword parameter as short as a few characters and returns matching hotels, hotel chains, and destinations. Use the subType query parameter (HOTEL_LEISURE, HOTEL_GDS) to scope results to specific inventories.

What are the rate limits for the Hotel Name Autocomplete API?

Amadeus enforces per-second and per-month transaction limits that depend on whether you are calling the test or production environment. Test base URL is test.api.amadeus.com/v1 with low-volume quotas suitable for development. Confirm your production tier in your Amadeus for Developers self-service workspace before launching.

How do I autocomplete a hotel name through Jentic?

Run pip install jentic, then search 'autocomplete a hotel name' through the Jentic SDK to discover this operation. Load its schema, then execute with keyword and subType parameters. Jentic returns the parsed hotelIds ready to chain into Hotel Search or Hotel Booking calls. Get started at https://app.jentic.com/sign-up.

Is the Hotel Name Autocomplete API free?

Amadeus offers a free self-service tier on test.api.amadeus.com that is suitable for prototyping. Production usage requires upgrading to a paid plan in the Amadeus for Developers portal; pricing depends on call volume and contract.

What data does each autocomplete result return?

Each result contains the matched name, the entity type (hotel or location), an IATA city code, geographic coordinates, and the Amadeus hotelId where applicable. This is enough information to populate a UI suggestion list and to seed the next call in a booking flow without further lookups.