Amadeus Hotel Ratings
Browse all Amadeus APIs✓ Official Vendor SpecData EnrichmentData Transformationoauth21 EndpointsREST
For Agents
Fetch aggregated guest sentiment scores by category for one or more Amadeus hotelIds, so agents can rank or filter hotels by review-based quality.
Use for: Get the sentiment score for a hotel by its Amadeus hotelId, Compare guest sentiment across a shortlist of hotels, Retrieve category-level sentiment for a hotel — room, service, location, Find which hotel in this list has the highest service score
Not supported: Does not return raw review text, prices, or bookings — use for aggregated hotel sentiment scores only.
The Amadeus Hotel Ratings API returns aggregated guest sentiment scores for hotels identified by Amadeus hotelIds. Each call returns an overall sentiment score together with a breakdown across categories such as service, room, location, and value, computed from review text mined across multiple sources. The single endpoint accepts up to several hotelIds at once and is designed to enrich booking interfaces, comparison shoppers, and ranking algorithms with quality signals beyond star ratings.
Install Jentic One Beta
Connect the Hotel Ratings to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hotel Ratings, 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.
1
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 | sh2
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 instanceJentic 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 Hotel Ratings API.
Retrieve overall sentiment score for a hotel from Amadeus's review aggregation pipeline
Break down sentiment by category — service, room, location, value, sleep, internet, catering
Compare quality signals across multiple hotelIds in a single GET call
Enrich Hotel Search offers with review sentiment to power ranking and filtering
Surface review-based scores alongside star ratings in booking UIs
Use Cases
Patterns agents use Hotel Ratings API for, with concrete tasks.
★ Ranking hotel search results by quality
After calling Hotel Search and receiving a list of offers, fetch sentiment scores for each hotelId and re-rank the results by overall sentiment or a specific category like cleanliness or location. The endpoint accepts a comma-separated list of hotelIds in a single request, so the enrichment step adds one round-trip rather than one per hotel. This is the difference between sorting by 'closest match' and sorting by 'highest review quality near you'.
Given hotelIds [TELONMFS, ADNYCCTB, HLLON101], call GET /e-reputation/hotel-sentiments and return the hotelId with the highest overall score.
Category-aware traveller filtering
Different travellers care about different things — a business traveller weights internet and sleep, a family weights catering and value. Hotel Ratings exposes per-category sentiment so the application can build trip-aware filters that surface hotels matching the traveller's actual priorities. Combine with Hotel Search to deliver a shortlist that reflects review-based fit, not just price.
Filter a shortlist of 20 hotels to only those with a service sentiment score above 80 and an internet score above 70.
Quality signal for AI travel recommendations
An AI-powered travel recommender uses hotel sentiment as one of several signals when explaining a recommendation to a user. The agent fetches sentiment via Hotel Ratings, combines it with price from Hotel Search and points-of-interest proximity, and produces a ranked recommendation with a citation: 'guests rate this hotel 88/100 for location and 91/100 for cleanliness'. This grounds AI-generated recommendations in real review data.
Use Jentic to search 'get hotel sentiment scores', load Hotel Ratings, execute with hotelIds=TELONMFS,ADNYCCTB and produce a ranked summary citing each category score.
Key Endpoints
1 endpoints — the amadeus hotel ratings api returns aggregated guest sentiment scores for hotels identified by amadeus hotelids.
METHOD
PATH
DESCRIPTION
GET
/e-reputation/hotel-sentiments
Get sentiment scores by Amadeus hotelIds
GET
/e-reputation/hotel-sentiments
Get sentiment scores by Amadeus hotelIds
Why 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; the long-lived client secret never enters the agent's context.
Intent-based discovery
Agents search by intent ('get hotel sentiment scores') and Jentic returns the Hotel Ratings operation with its hotelIds parameter and category response shape, so the agent can call it directly.
Time to first call
Direct Amadeus integration: 1-2 days for OAuth handling, retry logic, and response parsing. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Hotel Ratings API through Jentic.
What authentication does the Hotel Ratings API use?
OAuth 2.0 client credentials. Exchange your Amadeus API key and secret for a bearer token via the Amadeus authorization endpoint, then send it as the Authorization header on each call. Through Jentic, the client secret stays in the encrypted vault and the agent only ever receives a scoped token.
Can I retrieve sentiment for multiple hotels in one call?
Yes. The endpoint GET /e-reputation/hotel-sentiments accepts a comma-separated hotelIds query parameter, so you can fetch scores for a shortlist of hotels in a single round-trip rather than one call per hotel.
What categories of sentiment does the API return?
Each result includes an overall score plus per-category sentiment for service, room, sleep, value, location, internet, food, and points of interest. Scores are normalised to a 0-100 scale and are computed from review text aggregated across multiple sources.
What are the rate limits for the Hotel Ratings API?
Amadeus enforces per-second and monthly transaction limits that vary by environment. The test base URL test.api.amadeus.com/v2 has lower quotas appropriate for development; production tiers and quotas are set in your Amadeus for Developers contract.
How do I retrieve hotel sentiment through Jentic?
Install the SDK with pip install jentic, then search 'get hotel sentiment scores' to discover the Hotel Ratings operation. Load its schema, then execute with hotelIds. Jentic returns the parsed sentiment payload ready for ranking. Get started at https://app.jentic.com/sign-up.
Is the Hotel Ratings API available in the test environment?
Yes, but with restricted coverage — the test environment exposes a subset of production hotels (around 24 properties across London and New York). For broader coverage you must upgrade to the production tier in the Amadeus for Developers portal.
GET STARTED