Amadeus Self-Service vs FlightPowers, and when to migrate

curl -X GET "https://test.api.amadeus.com/v2/shopping/flight-offers?\
originLocationCode=SYD&destinationLocationCode=BKK&\
departureDate=2022-08-01&returnDate=2022-08-05&\
adults=2&includedAirlineCodes=TG&max=3" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

curl -X POST https://api.flightpowers.com/v1/flights/roundtrip \
  -H "x-api-key: $FLIGHTPOWERS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from_airport": "SYD",
    "to_airport": "BKK",
    "departure_date": "2026-10-19",
    "return_date": "2026-10-23",
    "passengers": [1, 1],
    "departure_airline_codes": ["TG"],
    "limit": 3
  }'

curl -X POST https://api.flightpowers.com/v1/flights/oneway \
  -H "x-api-key: $FLIGHTPOWERS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from_airport": "JFK",
    "to_airport": "LHR",
    "departure_date": "2026-11-12"
  }'

"search_status": "ok"
"search_coverage": { "requested_combinations": 1,
                     "searched_combinations": 1,
                     "truncated": false }

{
  "price_range_in_relation_to_other_periods": "high",
  "price_insights_low": 170,
  "price_insights_high": 285,
  "from_airport": "New York (JFK)",
  "to_airport": "London (LHR)",
  "departure_date": "2026-11-12",
  "price": "$291",
  "price_as_number": 291,
  "duration": "10 hr 25 min",
  "duration_seconds": 37500,
  "airline": "Icelandair",
  "stops": 1,
  "stops_info": [
    { "stop_airport": "KEF", "stop_duration_seconds": 5100 }
  ],
  "departure_description": "7:25 PM on Thu, Nov 12",
  "arrival_description": "10:50 AM on Fri, Nov 13",
  "buy_link": "https://www.google.com/travel/flights?tfs=..."
}

Both APIs handle round-trip in a single request, so there is no gain to claim there. The difference is that ours is a dedicated endpoint that returns paired legs with a combined total (total_price_as_number, total_duration_seconds, total_stops) plus separate departure_flight_* and return_flight_* blocks, and it accepts per-leg filters. “Leave after 6pm Friday, return before noon Sunday” is one call.

Self-Service had no cheapest-date search on Flight Offers Search: you looped. The REST API here works the same way, but the per-minute rate limits are published so you can parallelise deliberately: a 31-date scan is one burst, not a serial crawl (how that works). If you are building an AI agent, the hosted MCP server at https://flights.flightpowers.com/mcp does the fan-out for you: its flight search accepts a date range and a list of destinations and expands the combinations server-side. That is an MCP-layer feature, not a REST parameter; on REST you loop. See MCP setup.

# 1. get hotelIds for a city
curl -X GET "https://test.api.amadeus.com/v1/reference-data/\
locations/hotels/by-city?cityCode=PAR" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

# 2. price those specific hotels
curl -X GET "https://test.api.amadeus.com/v3/shopping/hotel-offers?\
hotelIds=MCLONGHM&adults=2&checkInDate=2026-10-19\
&checkOutDate=2026-10-23" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

curl -X POST https://api.flightpowers.com/v1/hotels/search \
  -H "x-api-key: $FLIGHTPOWERS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "destination": "Paris",
    "checkin_date": "2026-10-19",
    "checkout_date": "2026-10-23",
    "adults": 2,
    "currency": "EUR"
  }'

To look up one named property instead of searching a city, use POST /v1/hotels/by-name with hotel_name, checkin_date, checkout_date, and optionally area to disambiguate generic names.

1. Subscribe on RapidAPI (free tier) and confirm the key authenticates with GET /v1/verify.
2. Delete the OAuth token fetch, cache and refresh logic. Replace with one header.
3. Rename request fields per the tables above. Watch adults → passengers (a list) and travelClass → seat_type (only two cabins).
4. Rewrite response parsing: the shape is flat JSON, not Amadeus’s data[] / dictionaries envelope.
5. Drop the hotel ID-resolution step; pass destination as free text.
6. Re-point anything that booked to a booking platform. That work does not migrate.
7. Run your three hardest routes on both datasets before you cut over. GDS content and Google Flights content are not identical.

Did Amadeus Self-Service shut down?

Yes, on July 17, 2026. Amadeus posted the date itself on developers.amadeus.com, which reads “has been decommissioned on July 17th, this website is for Amadeus Enterprise API Portal only” (an archived copy from three days before the cutover gives the year: “will be decommissioned on July 17th, 2026”). What we can additionally verify ourselves, first on 2026-08-24 and again on 2026-09-07 with identical results: the Self-Service portal and pricing pages 301-redirect to the Amadeus homepage, the test sandbox host no longer resolves, all 20 repositories in the amadeus4dev GitHub organisation are archived, and their developer-guides README opens with “The Amadeus for Developers Self-Service offer has been deprecated.” The commands to check each of these yourself are on this page.

Should I move to Amadeus Enterprise instead?

If you are an accredited travel business (you hold IATA or ARC accreditation, or work through a consolidator), yes, Enterprise is the appropriate path and it is a serious platform. This page is for the people Enterprise is not designed to serve: indie developers, early-stage startups, internal tooling teams, researchers and AI-agent builders who chose Self-Service precisely because it was self-serve.

Does FlightPowers replace Flight Create Orders or the Hotel Booking API?

No. Nothing on our side issues tickets, creates PNRs, or confirms reservations. If the purchase happened inside your product, we are the wrong answer. Go to Amadeus Enterprise or a booking platform like Duffel. We replace the shopping endpoints: Flight Offers Search and Hotel List + Hotel Search.

Is the data the same as what Amadeus served?

No, and pretending otherwise would waste your afternoon. Amadeus served GDS-sourced content; we return live Google Flights consumer pricing and live Booking.com hotel rates. These are genuinely different datasets with different carrier coverage, and neither is a superset of the other. Run your three hardest routes on both before you cut over.

How does authentication change?

Amadeus used OAuth2 client credentials: fetch a token, watch it expire, refresh it. Here there is no token step: one static x-api-key header, with the key issued by RapidAPI when you subscribe. You can delete your token-refresh code and its cache.