GET recommended destinations in Amadeus Travel Recommendations
A documented Amadeus Travel Recommendations operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
GET recommended destinations
- GETReads data · recommended-locations
test.api.amadeus.com/reference-data/recommended-locations
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Amadeus Travel Recommendations operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Questions
- Can HumDay get recommended destinations in Amadeus Travel Recommendations?
- Yes. This operation is published in Amadeus Travel Recommendations's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Amadeus Travel Recommendations account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Amadeus Travel Recommendations.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Amadeus Travel Recommendations account.
Where this came from
Read from a published API description for Amadeus Travel Recommendations at raw.githubusercontent.com/amadeus4dev/amadeus-open-api-specification/main/spec/json/Travel. The description above is the provider’s own wording, not ours. Last published 2023-03-24.