Skip to content
FlightPowers
Get key

Guide

Amadeus flight offers, or live Google Flights fares?

Published September 5, 2026 · Updated September 6, 2026

Short answer: Amadeus for Developers Self-Service was decommissioned on July 17, 2026, per the notice Amadeus posted on its own portal (source below). Re-checked on 2026-09-05, its portal pages returned archived or 301 responses (test.api.amadeus.com has no DNS record, the amadeus4dev GitHub org is fully archived), so a price tracker needs a live extraction API instead. FlightPowers' Google Flights API returns the fare a traveler would pay plus price_insights_low/price_insights_high and a low/typical/high verdict in the same response, without being able to issue a ticket.

A price tracker has two jobs. Get the number a traveller would actually pay today, and decide whether that number is worth waking someone up for. Pick your source on those two jobs, not on which company is older.

Is Amadeus Self-Service still available?

Anyone answering this question in 2024 would have said "start on the Amadeus Self-Service free tier". That advice has expired, and the check takes four commands.

Amadeus itself says so, on its own portal. developers.amadeus.com currently shows an announcement banner: "Amadeus for Developers self-service portal has been decommissioned on July 17th, this website is for Amadeus Enterprise API Portal only." An archived copy of the same page from three days before the cutover states the year: "Amadeus for Developers self-service portal will be decommissioned on July 17th, 2026." Source: developers.amadeus.com (checked 2026-09-06); pre-announcement archived at web.archive.org, 2026-07-15.

Re-run on 2026-09-05: test.api.amadeus.com returns no DNS record, and neither does api.amadeus.com. developers.amadeus.com/self-service answers 301 to the portal root. The amadeus4dev GitHub org shows 20 of 20 repositories archived, and the developer-guides README still opens with "[DEPRECATED] ... The Amadeus for Developers Self-Service offer has been deprecated". Those are observations of the public internet on that date, and they are reproducible from a terminal in under a minute.

The enterprise Amadeus relationship is a real thing and is not what this page is about. If you can sign that contract, Flight Offers Search gives you bookable, fare-ruled content with a path to issuing a ticket, and nothing here replaces that.

What a tracker actually needs

A price a person could pay. Both kinds of source give you this, in different shapes. A GDS offer is a priced, ticketable itinerary. An extraction API returns what the traveller sees on the shopping page, which is what your user will compare your alert against when they click through.

Context for that price. This is the part people build themselves and shouldn't. Google computes a usual range for a route and dates for its own UI and it ships in the response:

{
  "price_range_in_relation_to_other_periods": "typical",
  "price_insights_low": 50,
  "price_insights_high": 110,
  "price": "$63",
  "price_as_number": 63,
  "airline": "Vueling | Iberia, British Airways",
  "buy_link": "https://www.google.com/travel/flights?tfs=GjwSCjIwMjYtMTEtMTgiIAoDTEhSEgoyMDI2LTExLTE4GgNCQ04qAlZZMgQ3NjQzagUSA0xIUnIFEgNCQ05CAQFIAZgBAg&curr=usd"
}

That is trimmed from a real LHR to BCN response run on 2026-09-04. The tracker knows on its first ever call that $63 is normal here, so it stays quiet. No history table, no cold start.

A link that survives the alert. A cheap fare the user has to re-find by hand is usually gone by the time they find it. buy_link reopens that exact itinerary.

What do you give up?

You give up booking. An extraction API reads a shopping page, so it cannot issue a ticket, hold a PNR, or tell you a fare rule. If your product ends in a purchase you own, you need a booking platform underneath regardless of where the tracking prices come from.

You also give up owning the signal. The band is Google's opinion about that route, not your users' behaviour and not your own booking data. If a proprietary fare model is your differentiator, this feeds the model rather than replacing it. And the band is not on every route, so you still need the null branch.

There is no application form on this side, which is the practical difference for a small team. A key comes from the RapidAPI listing with a free plan, and it works on the next request.

A tracker that has context on call one

Live fares with Google's own price range and a low, typical or high verdict on every result. Free tier on RapidAPI, no application form.

Get a key on RapidAPI →See pricing

Free tier: 10 requests/month. No card to try.