canonical: https://jentic.com/apis/amadeus-hospitality.com/amadeus-hospitality # Amadeus Hospitality API 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. ## For AI 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. ## Scope Does not handle flight booking, car rental, or guest loyalty programmes - use for hotel shop-and-book, group RFPs, and booking analytics only. ## Capabilities - 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 - List scheduled events with their associated property and date metadata - Submit a group request-for-proposal with attendee counts, dates, and preferred properties - Reconcile group business across shop, RFP, and room-block surfaces with a single bearer token ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Bookings Analysis** — GET aggregated booking pace and pickup metrics for revenue tracking. - **Shop and Book** — POST availability and rate searches across the property catalog. - **Room Blocks** — GET room blocks attached to group reservations and meetings. - **Events** — GET scheduled events with property and date metadata. - **RFP** — POST a structured group request-for-proposal to one or more properties. ## Why Jentic - **Setup:** Wiring the Amadeus Hospitality API by hand means setting up its bearer token against api.amadeus-hospitality.com/v1 and encoding the shop-and-book, RFP, and analytics calls yourself. Through Jentic you install once, import the Amadeus Hospitality API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** The Amadeus Hospitality API carries its search and booking targets in the request body and query rather than as path resources, so limit the agent to the operations it needs, such as shop-and-book search or reading booking analysis. You choose the operations it may call, so submitting an RFP is not included unless you add it. - **Credential handling:** Your Amadeus Hospitality bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search and book a hotel' or 'read booking analytics', and Jentic returns the matching Amadeus Hospitality operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Amadeus Hotel Search** — Self-service Amadeus hotel search aimed at developer integrations rather than hospitality contracts. - **Amadeus Hotel Booking** — Books a hotel offer that originated from Amadeus self-service hotel search. - **Amadeus Hotel Ratings** — Returns sentiment ratings for properties to enrich availability results. ## FAQ ### 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 (your Jentic One instance) 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. ### Can I limit what my agent is allowed to do with the Amadeus Hospitality API? Yes. Because you self-host Jentic One, your own rules decide which of the five Amadeus Hospitality operations the agent may call and which credentials it may use. You can grant read-only access such as shop-and-book search or reading booking analysis while leaving write actions like submitting an RFP off the list, since the agent only gets the operations you add. The search and booking targets travel in the request body and query rather than the path, so scoping is done at the operation level: the agent simply cannot invoke an endpoint you did not permit.