Amadeus Hospitality API

Name: Amadeus Hospitality API
Brand: Amadeus Hospitality API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementbearer5 EndpointsREST

For Agents

Search hotel availability, analyse bookings, and submit group RFPs through Amadeus Hospitality. Agents can pull room block and event data and create RFPs against the /rfp endpoint with bearer-token auth.

Install Jentic One Beta

Connect the Amadeus Hospitality API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amadeus Hospitality API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amadeus Hospitality API.

Search property availability and rates through the /shop-and-book/search endpoint

Pull aggregated booking analysis to compare pace and pickup against prior periods

Retrieve active room blocks tied to group reservations and meetings

GET STARTED

Start building with Amadeus Hospitality API

Explore with Jentic

View OpenAPI Document

The Amadeus Hospitality API gives hotels, distributors, and travel platforms programmatic access to booking analytics, room availability, group room blocks, events, and request-for-proposal workflows. It exposes a single bearer-authenticated surface that covers shop-and-book search across rates and properties, RFP creation for group business, and read access to room block and event inventory. The API targets hotel commerce teams and travel-tech integrators who need structured access to Amadeus Hospitality data without scraping or screen-scraping legacy GDS interfaces.

Use Cases

Patterns agents use Amadeus Hospitality API for, with concrete tasks.

★ Group RFP Submission

Submit a structured request-for-proposal for meetings and group business directly to Amadeus Hospitality from a CRM or sales tool. The /rfp POST endpoint accepts attendee counts, preferred dates, room requirements, and target properties, removing the need to email PDFs to each property. Sales teams can wire RFP creation into pipeline stages and surface property responses inside their existing system.

Create an RFP for 200 attendees at three preferred Frankfurt properties for September 15-17 and confirm the RFP ID returned by the API.

Shop and Book Availability

Power a booking widget or travel agent UI with live rate and availability lookups across the Amadeus Hospitality property catalog. The /shop-and-book/search POST endpoint takes check-in, check-out, and occupancy parameters and returns bookable rates. This replaces fragile scraping of brand sites and gives a single integration point for hundreds of properties.

Search /shop-and-book/search for 2 adults, check-in 2026-08-12, check-out 2026-08-15 at property code FRA001 and return the lowest available nightly rate.

Booking Pace Analytics

Track booking pace and pickup for revenue management by polling the /bookings/analysis GET endpoint. Revenue managers can chart how bookings are accumulating against the same period last year and adjust pricing or marketing spend in response. This use case keeps analytics dashboards fed without a manual export from the property management system.

Fetch /bookings/analysis for the last 30 days for property FRA001 and summarise pickup versus the prior 30-day window.

Agent-Driven Hotel Booking Workflow

Let an AI agent handle hotel discovery, RFP submission, and booking-pace reporting end to end through Jentic. The agent searches Jentic for the right Amadeus Hospitality operation, loads its schema, and executes the call with a vault-stored bearer token. This collapses what would otherwise require reading three separate sets of API docs into a single agent loop.

Use Jentic search for 'submit a hotel group rfp', load the /rfp schema, and execute it with attendee count 150 for property FRA001.

Key Endpoints

5 endpoints — the amadeus hospitality api gives hotels, distributors, and travel platforms programmatic access to booking analytics, room availability, group room blocks, events, and request-for-proposal workflows.

METHOD

PATH

DESCRIPTION

POST

/shop-and-book/search

Search availability and rates

GET

/bookings/analysis

Get booking pace and pickup analysis

POST

/rfp

Create a group RFP

GET

/room-blocks

List room blocks

GET

/events

List scheduled events

POST

/shop-and-book/search

Search availability and rates

GET

/bookings/analysis

Get booking pace and pickup analysis

POST

/rfp

Create a group RFP

GET

/room-blocks

List room blocks

GET

/events

List scheduled events

Why Jentic?

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

Credential isolation

The Amadeus Hospitality bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access at execution time and the raw token never enters the model context.

Intent-based discovery

Agents search Jentic by intent — 'search hotel availability' or 'submit a group rfp' — and Jentic returns the matching Amadeus Hospitality operation with its input schema, so the agent calls the right endpoint without browsing five separate doc pages.

Time to first call

Direct integration with Amadeus Hospitality: 3-7 days for bearer-token plumbing, error handling, and schema mapping across the five endpoints. Through Jentic: under one hour — search, load, execute.

FAQs

Specific to using Amadeus Hospitality API through Jentic.

What authentication does the Amadeus Hospitality API use?

The API uses bearer-token authentication. All five endpoints require an Authorization header with a bearer token issued by Amadeus Hospitality. Through Jentic the bearer token is stored in the encrypted vault (MAXsystem) and never enters the agent's prompt context.

Can I submit a group RFP with the Amadeus Hospitality API?

Yes. POST to /rfp with attendee counts, target dates, and preferred property codes to create a structured request-for-proposal. The endpoint replaces emailing PDFs and lets sales teams wire RFP creation directly into a CRM.

What are the rate limits for the Amadeus Hospitality API?

Rate limits are not declared in the OpenAPI specification and depend on the contract negotiated with Amadeus Hospitality. Treat shop-and-book searches as the most rate-sensitive call and cache results where possible. Confirm exact limits with the Amadeus Hospitality account team for production traffic.

How do I search hotel availability through Jentic?

Run pip install jentic, then use the Jentic search query 'search hotel availability' to surface the Amadeus Hospitality /shop-and-book/search operation. Load the schema, supply check-in, check-out, and occupancy values, and execute. The full search-load-execute loop replaces hand-coding the POST request.

Does the Amadeus Hospitality API expose booking analytics?

Yes. The /bookings/analysis GET endpoint returns aggregated pace and pickup data for use in revenue management dashboards. It does not expose individual reservation records — those stay inside the property management system.

Is the Amadeus Hospitality API free to use?

No. Access requires a commercial agreement with Amadeus Hospitality and is sold to hotels, distributors, and travel-tech partners. Pricing and SLA terms are negotiated per account rather than published in a public tier list.

Amadeus Hospitality API

Connect the Amadeus Hospitality API to your agent

Capabilities

Start building with Amadeus Hospitality API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs