Amadeus Self-Service alternatives: which ones you can actually get access to

Published September 1, 2026 · Updated September 6, 2026

Short answer: Amadeus for Developers Self-Service was decommissioned on July 17, 2026, per the notice Amadeus itself posted on developers.amadeus.com (source below). It is now fully gone: test.api.amadeus.com and api.amadeus.com have no DNS record, /self-service redirects to the homepage, and the amadeus4dev GitHub org is fully archived (checked 2026-09-04). The real alternatives are gated differently, from Duffel's instant self-serve booking access to RapidAPI marketplace extraction APIs like FlightPowers with no application at all, each quoted and dated from its own provider page.

Most "Amadeus alternatives" lists compare features. That is not the problem you have. If you built on Amadeus Self-Service, you were a solo developer or a small team, and what you need to know about each replacement is one thing: can you get a key today, or does someone have to approve you first?

So that is the column this page leads with. Every gate below is quoted from the provider's own live page with the URL and the date I read it. Where I could not read the page from my machine, I say so instead of filling the cell.

Disclosure up front: I run FlightPowers, which is the last row in the table. Read that row as a vendor describing his own product, and check the rest yourself.

Is Amadeus Self-Service still available?

No. Amadeus posted its own decommission notice on developers.amadeus.com. The live portal now reads: "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 earlier 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.

Here is what I can additionally observe from my own machine, re-run on 2026-09-04:

getent hosts test.api.amadeus.com
# (no output, no record)

getent hosts api.amadeus.com
# (no output, no record)

curl -sS -m 15 https://test.api.amadeus.com/v1/security/oauth2/token
# curl: (6) Could not resolve host: test.api.amadeus.com

curl -sS -o /dev/null -w "%{http_code} -> %{redirect_url}\n" \
  https://developers.amadeus.com/self-service
# 301 -> https://developers.amadeus.com/

gh api "orgs/amadeus4dev/repos?per_page=100" \
  --jq '"archived \([.[]|select(.archived)]|length) of \(length)"'
# archived 20 of 20

Both API hostnames have no A record. That matters more than the portal redirect, because a missing DNS record is not a paused account or an expired token. There is nothing at the address to authenticate against. The amadeus4dev/developer-guides README opens with "The Amadeus for Developers Self-Service offer has been deprecated."

Amadeus Enterprise is untouched and still a serious platform. If you hold IATA or ARC accreditation, or work through a consolidator, that is your path and nothing here argues otherwise. This page is for everyone Enterprise was never designed to serve.

What alternatives exist, and what's the gate on each?

Every row was read on 2026-09-05. The quote behind each gate is in the sources list underneath, with the URL.

Sources for every gate above

All read 2026-09-05. Two of these hosts answer 403 to plain curl from a datacenter IP and need a real browser to reproduce, which is noted where it applies.

• Skyscanner, under the heading "We cannot give access to:" lists "Students and other individuals working on a non-commercial basis", "Start-ups without a robust business plan and pre-developed product", and "Businesses with low-traffic websites (minimum of 100K monthly active users)". The product page adds "Our team reviews each application and will get back to you within two weeks." partners.skyscanner.net/contact/travel-api and partners.skyscanner.net/product/travel-api, both HTTP 200.
• Travelpayouts: "Access to the Flight Search API is only available to projects with at least 50,000 monthly active users (MAU)", "Requests from projects that do not meet this requirement are not considered, and we do not make exceptions", and "What to add in the request description: Screenshots confirming your website traffic." support.travelpayouts.com/hc/en-us/articles/210995808, HTTP 200 in a browser, 403 to plain curl behind Cloudflare.
• Kiwi Tequila: the whole rendered page at tequila.kiwi.com/portal/login reads "Enter your email address and we'll send you a magic link to log in", plus "If you have an interest in becoming our affiliate, get in touch with us at affiliates@kiwi.com". /portal/signup and the docs path both land on the same login. HTTP 200. I am not calling this invitation-only, because that is not their word. There is simply no route to create an account.
• Duffel: "Complete these two steps in order to get access to Live Mode", "Verify information for Know Your Customer (KYC) purposes", and "Once you've activated your account, live tokens will be enabled" (duffel.com/guides/getting-started). The search ratio is on duffel.com/pricing: "Excess Search is a fee that ensures you maintain a healthy search-to-book ratio of no more than 1500 searches to one order", with the fee itself listed as "$0.005 per excess search." Both HTTP 200. To be fair to them, Duffel Stays is not sales-gated: duffel.com/stays says "Get instant access" and "Available from your first booking with no negotiation needed."
• Ignav: ignav.com/pricing reads "1,000 requests free, then $2 per 1,000 successful requests. No monthly minimums. No rate limits", and "A request is a one-way, round-trip, or flexible fare search, a booking link lookup, or an airport search." The same page adds "1,000 one-time free requests" and "No monthly commitment", so unlike HasData's monthly renewal the grant does not come back (re-read 2026-09-06). The home page adds "1,000 free requests. No credit card required." HTTP 200. They are the closest thing on this page to what I sell, they are self-serve the same way, and they publish their own Amadeus migration guide, so leaving them out would have made this table less useful.
• HasData: hasdata.com/apis/google-flights-api reads "The free plan renews 1,000 credits every month, which is 66 flight searches with every field included. No credit card required." The pricing block's own plan data lists the Startup plan at $59/mo for 200,000 credits, and the page states its own unit as 15 credits per flight search, which works out to $4.43 per 1,000 searches on that tier. Basic is $119/mo for 1,000,000 credits, Growth is $249/mo for 3,000,000. They also run a hosted MCP server, linked from the same site. HTTP 200. Re-read 2026-09-06: the same page documents a priceInsights object with lowestPrice, typicalPriceRange, priceLevel ("low | typical | high right now") and priceHistory, and its FAQ reads "priceInsights returns the lowest fare, the typical price range for the route, whether prices are low or high right now, and a price history over time." Their round trips are documented too, with the return leg fetched by "a separate request using departureToken". Their pricing cards render the annual price by default under a "Billed annually / 2 months free" toggle; the monthly figures above come from the plan data on the same page.
• flight-mcp.com: the homepage reads "No card to start" and "Free includes 300 monthly cache misses. Lite includes 10,000 for $19, and Pro includes 30,000 for $49. Cached responses are free," plus, separately, "cache hits never consume your monthly plan calls." It exposes both a REST endpoint and an MCP flight_search tool, and an Open Cache section that reads "Search existing cached data through REST or MCP before creating an account" (re-read 2026-09-06). flight-mcp.com, HTTP 200.
• Tripgic: tripgic.com/pricing reads "One-Time API Activation", "Pay once to provision your API credentials, sandbox environment, and supplier connections", and "The activation charge is non-refundable once API credentials are provisioned." The $500 entry plan lists Car Rental and Activities; the Flight API starts at the $1,499 plan. HTTP 200.
• SerpApi: plan cards on serpapi.com/pricing read "Free / $0 / month / 250 searches per month" and "Starter / $25 / month / 1,000 searches per month". HTTP 200. They publish monthly buckets, not a per-search price, so this page does not print one.
• SearchApi.io: "Sign up for 100 free requests", "No credit card required. No commitment. Cancel anytime.", and a published unit price, "Developer Plan / $4 per 1,000 searches / $40 / month / 10,000 Searches". searchapi.io/pricing, HTTP 200.
• Scrapingdog: "Every account starts with 200 free credits and full access to all APIs, no credit card required", and the flights endpoint "Costs 5 API credits per request." scrapingdog.com/documentation/google-flights-api/, HTTP 200.
• FlightAPI.io: "Can I try the API for free on your website? Yes, you can just sign up and start testing it for free", and, from the same FAQ, "Can I book flights using this API? NO. You cannot book flights using our API. This API only tracks prices." flightapi.io, HTTP 200. Their pricing lives at /#pricing; /pricing is a 404.
• Amadeus: the live developers.amadeus.com portal carries its own announcement banner: "Amadeus for Developers self-service portal has been decommissioned on July 17th, this website is for Amadeus Enterprise API Portal only" (checked 2026-09-06). An archived copy from 2026-07-15, three days before the cutover, states the year outright: "Amadeus for Developers self-service portal will be decommissioned on July 17th, 2026." web.archive.org/web/20260715114814/https://developers.amadeus.com/. Separately, developers.amadeus.com/self-service and /register both return 301 to developers.amadeus.com/. The deprecation line is in raw.githubusercontent.com/amadeus4dev/developer-guides/master/README.md, HTTP 200. The branch is master; the main path 404s.

One I could not check: Zyla API Hub answers 403 from our IP, so there is no row for it rather than a row sourced from somebody else's summary.

A note on what these rows are not

This is a table about access, not about quality. SerpApi, SearchApi.io and Scrapingdog return Google Flights data the same way we do, and they are self-serve the same way we are, so if the only thing you need is a key today, they are real answers and the comparison moves to price and to what each response contains.

Duffel is not a worse choice than us. It is a different product. If you sell tickets, you need Duffel or Enterprise, and no amount of price data substitutes for that. What the search ratio tells you is that Duffel is priced for a product that books, so a monitoring workload is the wrong shape for it.

Why the gate is the column that matters

Feature tables make these look interchangeable. They are not, and the reason has nothing to do with features.

Amadeus Self-Service existed because someone at Amadeus decided a developer with a side project should be able to get a sandbox key without talking to anyone. When it went away, most of what remained had an approval step in front of it, and the approval step is usually calibrated for a company, not a person. An audience review assumes you already have an audience. A monthly-visitor minimum assumes you already have traffic. Seller verification assumes you are selling something.

If you are rebuilding a fare alert, a price calendar, a research notebook or an AI agent, you have none of those yet, and you cannot get them without the data. That is the loop this page exists to break.

Migrate from Amadeus in 10 minutes

This is the shopping half of Self-Service: Flight Offers Search and Hotel Search. It does not cover Flight Create Orders. Nothing here issues a ticket.

1. Get a key (about a minute)

Subscribe to the free BASIC tier on RapidAPI. There is no application form and no approval step: the key is live on the page as soon as you subscribe.

• Flights: Google Flights Live API
• Hotels: Booking Live API

2. Delete the OAuth code (about two minutes)

Amadeus used OAuth2 client credentials. Fetch a token, cache it, watch it expire, refresh it. Replace all of that with one header:

# Before
POST https://test.api.amadeus.com/v1/security/oauth2/token
# -> { "access_token": "...", "expires_in": 1799 }

# After: no token endpoint. One header on every request.
x-api-key: YOUR_RAPIDAPI_KEY

Confirm the key works with GET /v1/verify before you run a real search.

3. Rename the fields (about five minutes)

The full mapping, including hotels, is on the Amadeus comparison page.

4. Run it

Here is a real run, JFK to LHR on 2026-11-12, made against api.flightpowers.com at 12:18 UTC on 2026-09-04 and pasted unedited. It took 8.4 seconds and returned five itineraries. The prices were live at capture time and have moved since, which is the whole point.

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"
  }'

Response headers:

x-search-status: ok
x-search-results: 5
x-search-attempts: 1
x-search-combinations: 1

First of the five results:

{
  "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": "$295",
  "price_as_number": 295,
  "duration": "7 hr 10 min",
  "duration_seconds": 25800,
  "airline": "Virgin Atlantic | Air France, Delta, KLM",
  "stops": 0,
  "stops_info": [],
  "departure_description": "8:00 AM on Thu, Nov 12",
  "arrival_description": "8:10 PM on Thu, Nov 12",
  "buy_link": "https://www.google.com/travel/flights?tfs=..."
}

5. Read the three fields Amadeus never gave you

Look at the top of that response. $295 sits above a historical band of $170 to $285, so Google calls it high. That is a fare-watch trigger you can write on day one, without building a price history database first.

• price_range_in_relation_to_other_periods: "low", "typical", "high", or null
• price_insights_low / price_insights_high: the band behind that verdict
• x-search-status: separates "Google has no itineraries" from "the search did not finish". Amadeus returned an empty array for both, and so does almost everything else on this page

The band is null when Google shows none. Handle that case. How the verdict works · How search status works

6. Test your own routes before you cut over

Amadeus served GDS content. This is live Google Flights consumer pricing. Carrier coverage differs in both directions, and neither dataset is a superset of the other. Run your three hardest routes on both and compare against your Amadeus logs.

Try it before you sign up for anything

These run live against the same API, in the browser, with no key and no account:

• Flight Price Checker: one route, one date, with the verdict
• Cheapest Month to Fly: a whole month scanned in one go
• Cheapest Time to Fly: the same route across the year
• Round-Trip Planner: paired legs with a combined total
• Hotel Price Check: live Booking.com rates
• Hotel Price by Country: the same room, priced from several markets

Full list on free tools.

What none of this replaces

If your product completes the purchase, you need a booking platform, not a data API. Nothing here issues tickets, creates PNRs, or confirms reservations.

• Flight Create Orders, Hotel Booking API, order management, seat maps, ancillaries. Go to Amadeus Enterprise, or to a booking platform such as Duffel.
• NDC content, private fares, consolidator content. Amadeus Enterprise.
• Multi-city and open-jaw itineraries. We do one-way and round-trip only.
• Reference data: airports, airlines, cities, points of interest, transfers, activities. Not part of the product.

What we do replace is the shopping half: Flight Offers Search becomes POST /v1/flights/oneway or /roundtrip, and Hotel List plus Hotel Search collapse into POST /v1/hotels/search with a free-text destination, so the ID resolution step disappears.

What it costs

Quoted from the live RapidAPI listings, re-parsed on 2026-09-11 by a script that fails our build if the numbers drift. Current plans are always on /pricing.

Flights and hotels are separate subscriptions. One RapidAPI key works for both once you have subscribed to each. BASIC needs no card.

I am deliberately not quoting what Amadeus Self-Service used to cost. Its pricing page now redirects to the homepage, so I have nothing live to quote, and a price I cannot source is a price I will not print.

Questions

Is 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 I can additionally verify myself, on 2026-09-04: test.api.amadeus.com and api.amadeus.com have no DNS record, /self-service 301s to the homepage, and all 20 amadeus4dev repositories are archived with a deprecation notice in the README. The commands are at the top of this page.

Which alternatives can I actually sign up for today, with no approval? From the table above: FlightPowers and SerpApi are self-serve. Duffel gives you a sandbox immediately but gates production behind verification. Kiwi, Skyscanner and Travelpayouts each require someone to approve you first.

Is there a flight price API with no approval process? Yes. A RapidAPI listing is self-serve by construction: you subscribe, the key appears, you call it. That is what FlightPowers is, and it is what SerpApi's Google Flights endpoint is too. The trade is that neither returns GDS content or lets you issue a ticket.

Can I book flights with FlightPowers? No. It is a data API. Every result carries a buy_link into Google Flights, and every hotel result a link into Booking.com, but the purchase happens there. If your product issues tickets, use Duffel or Amadeus Enterprise.

Should I move to Amadeus Enterprise instead? If you are an accredited travel business and you need booking and ticketing, yes. If you chose Self-Service precisely because it was self-serve, Enterprise is not a smaller version of the same thing.

Is the data the same as what Amadeus served? No. Amadeus served GDS-sourced content. This is live Google Flights consumer pricing and live Booking.com rates. Google Flights includes low-cost carriers with no GDS presence, and GDS carries fares Google never shows. Run your own routes on both.

How does authentication change? Amadeus used OAuth2 tokens that expired inside half an hour. Here it is one static x-api-key header. Delete the refresh code and its cache.

What about hotels? Same split. Live Booking.com rates for search and comparison, including per-country pricing. For a confirmed reservation, a booking platform.

Related

• FlightPowers vs Amadeus Self-Service, the full parameter mapping
• How to get a Google Flights API key
• The best flight data APIs in 2026
• FlightPowers vs Duffel
• FlightPowers vs SerpApi
• Free tools, all of them live, none of them needing a key