Hotel Booking

Name: Hotel Booking API
Brand: Hotel Booking
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementoauth21 EndpointsREST

For Agents

Create a real hotel reservation from a confirmed Amadeus hotel offer, returning provider confirmation numbers an agent can hand back to the traveller.

Quickstart

Get started with Hotel Booking 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:
"book an Amadeus hotel offer"

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

Capabilities

What an agent can do with Hotel Booking API.

Create a hotel reservation from a confirmed Amadeus hotel offer id

Submit guest names, contact details, and payment information in a single call

Return provider confirmation numbers and the Amadeus booking id for the reservation

Support multi-room bookings on the same offer in one request

GET STARTED

Start building with Hotel Booking API

Explore with Jentic

View OpenAPI Document

The Amadeus Hotel Booking API turns a confirmed hotel offer into a real reservation with the underlying hotel provider. The single POST endpoint takes an offer id from Hotel Search, traveller and guest details, plus payment information, and returns one or more booking ids and provider confirmation numbers. It is the final step in the Self-Service hotel flow and submits real reservations against live hotel inventory, so test bookings should never run against the production environment.

Use Cases

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

★ Confirm a Hotel Reservation End-to-End

After a user picks a hotel offer from Hotel Search, the integrator posts the offer id together with guest details and payment information to /booking/hotel-bookings. The response includes the Amadeus booking id and the provider's confirmation number, which the integrator stores and shows on the confirmation page.

POST a confirmed hotel offer with one guest (name, email, phone) and credit card details to /booking/hotel-bookings and return the Amadeus booking id and provider confirmation.

Multi-Room Family Booking

Travel agencies booking two adjoining rooms for a family submit a single hotel-bookings call with the matching offer ids and one set of guest details per room. The response carries one booking id per room together with provider confirmations, simplifying the manage-booking experience.

Create two hotel bookings on the same property by submitting two offer ids and per-room guest details in a single call to /booking/hotel-bookings.

Corporate Travel Hotel Reservation

Corporate booking tools call Hotel Booking with the corporate traveller's profile data and a corporate credit card token issued by the integrator's PSP. The Amadeus booking id and provider confirmation are written to the traveller's expense record and the on-property folio is reconciled later via the corporate program.

Book a single-night hotel stay for a corporate traveller in NYC using a stored offer id and a tokenised corporate card.

Agent-Driven Hotel Booking via Jentic

An AI travel concierge that searches Amadeus hotel inventory uses Jentic to call the Hotel Booking endpoint once the user confirms. Jentic resolves OAuth and validates the offer, guest, and payment payload against the operation schema, returning the booking id the agent can show the user.

Call jentic.search('book an Amadeus hotel offer'), load the operation, and execute it with offerId, guests, and payments to return the Amadeus booking id.

Key Endpoints

1 endpoints — the amadeus hotel booking api turns a confirmed hotel offer into a real reservation with the underlying hotel provider.

METHOD

PATH

DESCRIPTION

POST

/booking/hotel-bookings

Create a hotel reservation from a confirmed offer

POST

/booking/hotel-bookings

Create a hotel reservation from a confirmed offer

Why though Jentic?

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

Credential isolation

Amadeus client_id and client_secret are stored encrypted in the Jentic vault. Jentic runs the OAuth 2.0 client_credentials exchange and refreshes the bearer token automatically before each booking call, so the agent never handles raw secrets.

Intent-based discovery

Agents search Jentic by intent ('book an Amadeus hotel offer') and Jentic returns the /booking/hotel-bookings operation with its required offerId, guests, and payments shapes.

Time to first call

Direct Amadeus integration: 3-5 days for OAuth, payload shaping, and provider confirmation handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Hotel Search

Returns the offer ids this API consumes.

Use upstream to find available offers for the user's dates and city before calling Hotel Booking.

Complementary

Hotel Name Autocomplete

Resolves user-typed hotel names into Amadeus hotel ids.

Use upstream of Hotel Search when the user types a hotel name rather than a city.

Complementary

Hotel Ratings

Returns sentiment scores and ratings for a hotel id.

Use after Hotel Search to enrich offers with ratings before the user confirms a booking.

Alternative

Flight Create Orders

Same booking pattern, but for flights instead of hotels.

Use when the agent needs to book a flight rather than a hotel; both endpoints share the OAuth flow and the priced-offer-then-book sequence.

FAQs

Specific to using Hotel Booking API through Jentic.

What authentication does the Hotel Booking API use?

Amadeus Self-Service OAuth 2.0 client_credentials. Exchange your client_id and client_secret at https://api.amadeus.com/v1/security/oauth2/token for a bearer token and pass it in the Authorization header. Through Jentic, the credentials live in the encrypted vault and the bearer token is rotated for you on each call to /booking/hotel-bookings.

Should I use this API in the test environment for live testing?

No — Amadeus warns against running test bookings against production, since real reservations are sent to hotel providers and excessive cancellations can get an integrator blacklisted. Use the test base host (test.api.amadeus.com) with sample offer ids during development.

What are the rate limits for the Hotel Booking API?

Amadeus Self-Service Test environment caps booking endpoints at 1 transaction per second per API key with a monthly quota; Production limits scale with your Self-Service plan tier. Bearer tokens themselves expire after roughly 30 minutes.

How do I create a hotel booking through Jentic?

Run pip install jentic, then call jentic.search('book an Amadeus hotel offer'), load the operation, and execute it with offerId, guests, and payments. Jentic posts to /booking/hotel-bookings and returns the Amadeus booking id and provider confirmation.

Does this API charge the guest's credit card?

Card details submitted here are forwarded to the hotel provider for processing under the offer's payment policy (deposit, full charge, or pay-at-property). The integrator should still tokenise card data through its own PSP for storage and PCI scope, rather than persisting raw card numbers.

How do I cancel a hotel booking I just created?

Cancellation is not part of this API. Use the hotel provider's cancellation flow via the confirmation number returned in the booking response, or the Amadeus Self-Service Hotel Order Management endpoints if your account has access.