Best Travel API in 2026: Access Gates, Coverage, and What Each One Returns

The best travel API is not the one with the nicest JSON. It is the one whose door still opens for you. Most comparison posts list features and skip the access gate, which is the thing that actually kills a sprint in week two.

This page compares what each API returns, who can get a key, and which verticals it covers. Ktemia’s own contract is in the flight search API post: one POST, three required fields, routes not live yet.

Key Takeaways

• Amadeus decommissioned its self-service developer portal on 17 July 2026. Enterprise APIs remain.
• Skyscanner, Expedia Rapid, and Booking.com Demand all gate access behind review or an affiliate agreement.
• CarTrawler publishes mobile SDKs, not a documented public REST endpoint.
• There is no official public Google Flights API. QPX Express closed in 2018.

Travel API comparison at a glance

API	Verticals	Access gate	What you get
Ktemia	Flights, hotels, cars, property	Open signup, Free tier	100+ providers across four verticals on one contract, plus MCP and a copilot
Amadeus	Flights, hotels, cars	Enterprise only since July 2026	Full GDS-grade stack, account-managed
Skyscanner	Flights, car hire	Partnerships application	Live Prices, create-then-poll
Kiwi Tequila	Flights	Affiliate / B2B agreement	Search and deep links, separate booking chapter
Booking.com Demand	Accommodation	Affiliate ID + bearer token	/accommodations/search, availability, reviews, sandbox
Expedia Rapid	Lodging, cars	Certified partner programme	Shop, price check, book, manage
CarTrawler	Cars	Partner clientId	Android, iOS, Flutter, React Native SDKs
Sabre	Flights, hotels, cars	Enterprise / GDS	Shopping and booking, account-managed

Read that access column before the feature columns. Four of the eight options above cannot be evaluated this afternoon — they need an application, a business review, or a certified implementation partner. A travel API you cannot get a key for is not a shortlist candidate, however good the documentation looks.

Ktemia: four verticals on one contract

Ktemia compares more than 100 providers across flights, hotels, car rental, and property. The point is not the provider count on its own. It is that one key and one required-field pattern covers all four verticals, so adding car rental to a product that already searches flights is a different endpoint rather than a different integration, a second contract, and a second schema to normalise.

What ships with it:

• POST /v1/flights, POST /v1/hotels, POST /v1/cars — same shape, per-vertical required fields
• An MCP server, so an agent in Cursor or Claude can run the search without a developer assembling each call
• An AI copilot that asks for a missing field instead of guessing a city or a date
• Connectors into Zapier, Webhooks, PostgreSQL, Snowflake, Salesforce, and Slack
• The Free plan is free and includes dashboard search

Routes are not live yet. When they are, this page gets a dated response rather than an invented one.

The MCP piece is worth isolating. Agent-driven travel search is being built right now, and almost none of the incumbents above ship an MCP server. If that is your product, the shortlist is much shorter than this table suggests. The wiring is in flights MCP.

Amadeus: the self-service door closed in 2026

In February 2026, PhocusWire reported that Amadeus would pause new self-service registrations and then decommission that portal on 17 July 2026. Keys disabled, portal gone. The Enterprise portal and Enterprise APIs were explicitly left standing.

Any tutorial telling you to grab a free key at test.api.amadeus.com is describing a door that no longer exists. Remaining Amadeus access is an enterprise conversation. The full picture is in Amadeus API vs Skyscanner API.

Skyscanner: partner review, then create-and-poll

Skyscanner’s Flights Live Prices is a genuine search API — origin, destination, date in; fares out — built on two POSTs: /create opens a session, /poll/{sessionToken} returns the full list.

You do not get a key by reading the docs. Skyscanner’s authentication page says you submit an application to Partnerships, and their partner support is blunt that a key arrives only after the Partners team approves a business proposal. Their Travel API product page is aimed at established businesses with a large audience.

Booking.com Demand: the most documented accommodation option

Booking.com’s Demand API covers accommodation properly: /accommodations/search, /accommodations/availability, /accommodations/bulk-availability, plus /details, /reviews, and /chains. Authentication is a bearer token with an X-Affiliate-Id header, and there is a documented sandbox at demandapi-sandbox.booking.com.

That sandbox matters more than it sounds. Most options in this table give you nothing to call until a commercial conversation finishes. Detail is in Booking.com API.

Expedia Rapid: a four-step transactional flow

Rapid is sequential, not a single call: Shopping returns rooms with rates and cancellation policies, Price Check validates the rate and returns either MATCHED or a revised price, Booking completes it, and Retrieve/Manage handles the itinerary afterwards.

The price-check step is the one that catches teams out. Rates can move between shopping and booking, so you must re-validate rather than trust the rate you displayed. If you are building comparison rather than transaction, that whole loop is overhead you do not need. Expedia also routes development through Elite and Preferred technology partners, so “just sign up” is not the model. See Expedia API alternative.

CarTrawler: SDKs, not a REST endpoint

CarTrawler’s public documentation covers Android, iOS, Flutter, and React Native SDKs, with a Vehicles API reached through the SDK and gated behind a clientId. There is no documented public REST endpoint.

If your stack is a backend service, an SDK-shaped integration is a real architectural constraint, not a detail. Car rental options are in car rental API.

How to choose

Four questions, in this order:

1. Can you get a key? Open signup, affiliate agreement, partner review, or enterprise contract. This eliminates most of the table for most teams.
2. How many verticals? One vertical means one integration. Four verticals through four vendors means four schemas, four keys, and four sets of rate limits.
3. Search or transaction? A comparison product does not need Rapid’s price-check-then-book loop.
4. Are agents in scope? If yes, MCP support moves from nice-to-have to the deciding factor.

Price variance is the reason this matters at all. We priced 1,703 flights across 57 booking sites and found a $970 median spread on the identical seat. Any single source gives you one of those numbers and no way to know where it sits.

Pick the door that opens, then the coverage.

The best travel API in 2026 is whichever one you can actually call, that covers the verticals you ship, in the shape your stack wants. For most teams that eliminates the GDS tier immediately and turns the decision into coverage and integration cost.

Caps sit on pricing. The four verticals are on use cases. Routes are not live yet.