Hotel Search API

Name: Hotel Search API API
Brand: Hotel Search API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth22 EndpointsREST

For Agents

Fetch live hotel offers and pricing for a set of Amadeus hotelIds, returning bookable offerIds, room descriptions, and cancellation rules ready to pass to Hotel Booking.

Quickstart

Get started with Hotel Search API 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:
"search hotel offers"

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

Capabilities

What an agent can do with Hotel Search API API.

Retrieve hotel offers for up to many hotelIds in a single getMultiHotelOffers call

Filter offers by check-in and check-out dates, adults, room quantity, and currency

Re-price a specific offerId before booking using getOfferPricing

Surface board type, cancellation policy, and total price for each room offer

GET STARTED

Start building with Hotel Search API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Hotel Search API API for, with concrete tasks.

★ Multi-hotel comparison shopper

Power a hotel comparison page that takes a shortlist of properties (typically 10-50 hotelIds from a previous search step) and returns live offers for each, enabling side-by-side comparison of price, room type, and cancellation flexibility. The getMultiHotelOffers endpoint accepts the hotelIds list and stay parameters and returns a structured offers array, so the front-end can render comparison cards without fan-out calls.

Call GET /shopping/hotel-offers with hotelIds=TELONMFS,ADNYCCTB,HLLON101 checkInDate=2026-07-01 checkOutDate=2026-07-04 adults=2 and return each hotel's lowest total price.

Pre-booking price confirmation

Before charging a customer, hotel sites must re-confirm the offer is still available at the quoted price — rates change frequently and an offer surfaced in a search result may already be stale. The getOfferPricing endpoint re-prices a specific offerId and returns the current rate plus full booking metadata. This is the standard last step before invoking Hotel Booking to commit the reservation.

Call GET /shopping/hotel-offers/{offerId} for offerId=B5GHX3 and verify the total price still matches what was shown to the user.

Date-flexible availability scan

Some travellers care more about getting a specific hotel than a specific date. Sweep getMultiHotelOffers across a range of check-in dates for a single hotelId to find when the property has availability and at what rate. Combine with Hotel Ratings to surface highly-rated alternatives if the preferred hotel is unavailable. Useful for concierge agents and travel research assistants.

For hotelId=TELONMFS, call /shopping/hotel-offers across 14 consecutive check-in dates and return all dates with at least one bookable offer.

AI agent booking flow

An AI agent handling 'book me a room in Paris next Friday for two nights' uses Hotel Search to fetch concrete offers after the user has chosen a hotel via Autocomplete and Ratings. The agent calls Jentic to discover Hotel Search, executes it with the user's parameters, presents the cheapest cancellable offer for confirmation, then re-prices it via getOfferPricing before chaining to Hotel Booking.

Use Jentic to search 'search hotel offers', execute Hotel Search with hotelIds, dates, and adults parameters, and return the lowest cancellable offer for user confirmation.

Key Endpoints

2 endpoints — the amadeus hotel search api returns live hotel offers — rates, room types, board options, cancellation policies — for a list of amadeus hotelids and a stay window.

METHOD

PATH

DESCRIPTION

GET

/shopping/hotel-offers

Get offers across multiple hotelIds for a stay

GET

/shopping/hotel-offers/{offerId}

Re-price a specific hotel offer by offerId

GET

/shopping/hotel-offers

Get offers across multiple hotelIds for a stay

GET

/shopping/hotel-offers/{offerId}

Re-price a specific hotel offer by offerId

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 scoped bearer tokens at execution time; the client secret never enters the agent's context or logs.

Intent-based discovery

Agents search by intent ('search hotel offers') and Jentic returns Hotel Search with its hotelIds, date, and pax parameter schemas, so the agent can call it without parsing the Amadeus reference docs.

Time to first call

Direct Amadeus integration: 3-5 days for OAuth, offer re-pricing flow, error mapping, and pagination. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amadeus Hotel Booking

Hotel Booking commits an offerId returned by Hotel Search into a confirmed reservation.

Choose Hotel Booking immediately after Hotel Search and offer re-pricing to commit the user's reservation.

Complementary

Amadeus Hotel Name Autocomplete

Resolve free-text hotel keywords into the hotelIds Hotel Search needs as input.

Choose Hotel Name Autocomplete when you have a name string but not a hotelId to feed Hotel Search.

Complementary

Amadeus Hotel Ratings

Hotel Ratings enriches the offers returned by Hotel Search with sentiment scores for ranking.

Choose Hotel Ratings to re-rank Hotel Search results by review quality before showing them to the user.

FAQs

Specific to using Hotel Search API API through Jentic.

What authentication does the Hotel Search API use?

OAuth 2.0 client credentials. Exchange your Amadeus API key and secret for a bearer access token, then pass it as the Authorization header on each call. Through Jentic, the client secret stays encrypted in the vault and the agent only ever receives a scoped bearer token.

Can I search offers across many hotels in one call?

Yes. GET /shopping/hotel-offers accepts a comma-separated hotelIds parameter so you can fetch live offers for a shortlist of hotels in a single request. This is the recommended pattern for comparison shoppers and multi-hotel result pages.

Why do I need to re-price an offer before booking?

Hotel rates change frequently. The /shopping/hotel-offers/{offerId} endpoint re-confirms the current price and availability for a specific offerId before you commit it to Hotel Booking. Skipping this step often results in price-mismatch errors at booking time.

What are the rate limits for the Hotel Search API?

Amadeus enforces per-second TPS and monthly transaction quotas that depend on environment and contract. Test (test.api.amadeus.com/v3) has low quotas suitable for development; production limits are set in your Amadeus for Developers contract.

How do I search hotel offers through Jentic?

Install with pip install jentic, then search 'search hotel offers' to discover the Hotel Search operation. Load its schema, then execute with hotelIds, checkInDate, checkOutDate, and adults parameters. Jentic returns the parsed offers ready to display or chain into Hotel Booking. Get started at https://app.jentic.com/sign-up.

Does the test environment cover all hotels?

No. The Amadeus test environment offers only a subset of production hotels and may change dynamically. For prototyping, test against major-city hotelIds like those in London (LON) or New York (NYC); upgrade to production for full inventory.