Head to head · Hotel and stay search · October 2026 research run

Booking.com Demand API vs Skyscanner Travel APIs

Booking.com Demand API scores 48.7 (D) on agent readiness against Skyscanner Travel APIs's 26.5 (F), and leads in 4 of 7 scored categories. Skyscanner Travel APIs leads on security & auth and payments & pricing. Both do hotel and stay search.

Best travel search and booking APIs for AI agents · All 120 travel comparisons

Which one, for what

Booking.com Demand API D

Best for An affiliate that already holds Booking.com credentials and wants its agent to book stays, cars and attractions.

Ahead on

  • Schema & documentation, 92 against 0
  • Agent ergonomics, 68 against 14
  • Maintenance & community, 48 against 10
  • Transparency & trust, 53 against 47

Watch for

Managed Affiliate Partner status required; no self-serve key

Skyscanner Travel APIs F

Best for An established travel site or app with a large audience that wants metasearch prices across flights, hotels and car hire and is content to send users to suppliers to book.

Ahead on

  • Security & auth, 43 against 36
  • Payments & pricing, 38 against 8

Also in its favour

  • Rated higher by the reviewer agents, 2.5 against 1.5 out of 5

Watch for

Keys go only to approved businesses with more than 100,000 monthly visits, after an application review and a commercial agreement

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Booking.com Demand API +92

Booking.com Demand API 92

The API references page links a stable OpenAPI specification for 3.3, 3.2 and 3.1 and one for Beta, and each reference page carries a "Download OpenAPI description" link. The 3.3 file, read on 10 November, is OpenAPI 3.1.0 with 44 paths, production and sandbox servers and 400, 401, 403, 404, 409 and 500 responses (25). developers.booking.com/llms.txt lists 202 Demand API pages, each with a Markdown copy (10). Reference pages state what each endpoint is for and the guides cover the search, look and book flow (15 of 20). Typed request bodies with required fields and enums in the references (12 of 15, held). Examples in the quickstart and references, and an error guide (last updated about five months before this check) tables every status code with causes and fixes, plus client error codes and payment errors (15). Numbered stable versions with a written lifecycle policy and a dated monthly changelog (15). Total 92.

Skyscanner Travel APIs 0

Every line rested on the developer docs at developers.skyscanner.net (the Redoc reference, overview pages, FAQ and changelog), whose robots.txt answered 403 Access Denied on 8 October. Those readings are struck. The partner help centre has no API reference, schema, examples or changelog. Contract (0), llms.txt or Markdown docs (0), descriptions (0), typed inputs (0), examples and errors (0), versioning and changelog (0). Total 0.

Agent ergonomics Booking.com Demand API +54

Booking.com Demand API 68

Search takes filters, and the rate-limiting guide documents the extras field to choose which blocks (facilities, photos, policies, rooms and more) search and details return, and rows to cap page size, with no summary mode (20 of 25). Pagination and filters on search, per the 30 September check and the same guide (18 of 20). Errors return a request_id and an errors array with a machine-readable id and a message with a suggested fix, and the guide says which codes to retry and which not to (20). No idempotency key on orders found; a duplicated order returns 409 and the guide says to check orders/details (5 of 20, held). Two auth headers on every call, no official SDKs (5 of 15). Total 68.

Skyscanner Travel APIs 14

The developer docs readings are struck (robots.txt refusal recorded on 8 October). Response sizing, paging and filters were read only there (0 and 0). The help centre documents one error, the 429 message, which isn't enough to recover from other failures (0). The help centre says the API can't take payment details or bookings, so every call is a read and retries are safe (14 of 20, partial carried). Required parameters and defaults were read only on the struck docs, and no SDK was found in any language (0). Total 14.

Maintenance & community Booking.com Demand API +38

Booking.com Demand API 48

The changelog's newest entry is October 2026, the release of version 3.3 with new accommodation, order, car and attraction capabilities and the Status API dashboard. Entries are dated by month only, so it can't show a change within 30 days (20). Dated entries since 12 August cover August, September (request-to-book indicator, cardless car orders, a 90-day attractions date range) and October 2026, more than three in all (20). Public changelog and partner account managers; no public support channel (8 of 15). No official SDKs (0). No package to judge (0). Total 48.

Skyscanner Travel APIs 10

The changelog at developers.skyscanner.net is struck with the rest of that host (robots.txt 403 on 8 October), and no other dated API change from Skyscanner was found. Help centre article dates record no change (0). No dated entry readable in the 90 days from 7 August (0). A partner help centre and a support request form, with support otherwise through account managers (10 of 15, partial carried). No current official SDK found (0 of 15). No package to assess (0 of 10). Total 10.

Payments & pricing Skyscanner Travel APIs +30

Booking.com Demand API 8

No x402, MPP or L402 (0). No published prices; commission terms are in the affiliate agreement behind Partner Centre (0). The sandbox is free but needs Managed Affiliate Partner status first, and payment tests need a real card (5 of 20). A person registers as a partner (0). Total 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Skyscanner Travel APIs 38

No x402, MPP or L402 (0). The help centre, re-read on 5 November, says the Travel APIs are free to use with no fee per booking and no yearly or monthly fee, and that partners earn commissions on a revenue share basis, without publishing the share (15 of 20). Use is free with no card, but only after an approved application and a commercial agreement, so half (10 of 20). A person applies on a form, the Partners Team reviews the business and an account manager runs onboarding on impact.com (0). Total 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Security & auth Skyscanner Travel APIs +7

Booking.com Demand API 36

Per the 30 September check, not re-read on 10 November, except where stated. A Bearer API key plus X-Affiliate-Id, generated in Partner Centre, shown once, with guidance to rotate yearly and revoke on compromise. No scopes found (20). The sandbox is the only reduced-privilege mode, and sandbox payment tests use a real card with temporary charges (5 of 20). Responses carry property descriptions and guest content written by third parties, with no injection guidance (5 of 15). Error responses carry a request_id for support, with no per-call log or audit view documented (3 of 15). developers.booking.com/.well-known/security.txt returned 404 on 30 September, and www.booking.com is closed to our reader, so the wider disclosure programme is unchecked (3 of 20, held). Total 36.

Skyscanner Travel APIs 43

The help centre says an API key comes only after the Skyscanner Partners Team approves a business proposal, with an account manager running onboarding. No scopes, self-serve rotation or OAuth found (15 of 30, partial carried). The API takes no payment details or bookings, so a leaked key can't spend money (12 of 20). The third-party text the API returns (hotel reviews and supplier content) was read only on the struck docs, and no injection guidance was found (0). The impact.com Partner Platform gives partners performance reports, with no per-call log found (3 of 15). Per the 8 October check, not re-read on 5 November, www.skyscanner.net carries a security.txt valid to 2030-11-20, a vulnerability disclosure policy and a public Bugcrowd bounty. Certifications not checked (13 of 20, partial carried). Total 43.

Transparency & trust Booking.com Demand API +6

Booking.com Demand API 53

Closed service. The affiliate terms sit behind Partner Centre sign-in, so the contract can't be read before you sign (5 of 30). The partner privacy statement names Booking.com B.V., Amsterdam, as the responsible entity; the consumer privacy page is closed to our reader and no retention periods or DPA were found, per the 30 September check (12 of 30). A written lifecycle policy (each autumn's stable release freezes the previous version, breaking changes only in a new stable version with a migration guide, promoted Beta capabilities retired after three months) and dated notices, such as the May 2026 deprecation of likeliness_rent_again with removal scheduled for 3.3. No notice period is stated for retiring a stable version (15). No subprocessor list or data locations found (3 of 20). Total 35.

Skyscanner Travel APIs 47

Closed service. The help centre says the Skyscanner API Terms and Conditions are in each partner's contract on impact.com, so they aren't public (8 of 30, partial carried). The privacy policy names Skyscanner Limited and says data is kept as long as needed, with no periods and no partner DPA found, per the 8 October check (12 of 30). No deprecation policy, and the dated changelog notices were read only on the struck developer host (0). The privacy policy lists processor categories without names or locations, per the 8 October check (5 of 20). Total 25.

Score by category

CategoryWeightBooking.com Demand APISkyscanner Travel APIsEdge
Reliability16%3335Skyscanner Travel APIs +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%920Booking.com Demand API +92
Agent ergonomics13%6814Booking.com Demand API +54
Security & auth14%3643Skyscanner Travel APIs +7
Payments & pricing10%838Skyscanner Travel APIs +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4810Booking.com Demand API +38
Transparency & trust7%5347Booking.com Demand API +6
Negative events≤1500
TotalD 48.7/100F 26.5/100

Facts side by side

FactBooking.com Demand APISkyscanner Travel APIs
KindHTTP APIHTTP API
VendorBooking.comSkyscanner Limited
Hosted endpointhttps://demandapi-sandbox.booking.com/3.2https://partners.api.skyscanner.net
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingYour planFree
x402nono
LicencenoneProprietary service. The API terms are in the partner contract and are not public
Read-only variant documentednono
llms.txtyesno
Last releasenone2026-10-01
Terms last updatedno document linkedno document linked
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot read yetyes
Agent reviews1.5/5 (2)2.5/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Booking.com Demand API

Booking.com's Demand API covers search, look and book and order management for stays, cars and attractions, with downloadable OpenAPI files, llms.txt, a documented error model and a written version lifecycle. Access needs Managed Affiliate Partner status, and there is no public status history, SLA, published price or idempotency key for orders.

Skyscanner Travel APIs

Skyscanner's partner APIs return flight, hotel and car hire prices with deep links to suppliers, with no usage fee and published rate limits. Access needs an approved application, more than 100,000 monthly visits and a commercial agreement. The developer docs refuse automated readers, so no contract, reference or changelog was graded, and booking happens on supplier sites.

Before you call either

Booking.com Demand API

  1. Send both Authorization: Bearer and X-Affiliate-Id, or the call fails on auth
  2. Stay under 50 requests a minute in the sandbox and back off exponentially on 429 and 5xx, with a capped retry count
  3. Before retrying a failed /orders/create, check /orders/details; a duplicated order returns 409
  4. Pick a version path (/3.3 for new work) and read the 3.3 migration guide, as 3.3 removes fields 3.2 still returns
  5. Use extras, filters and rows on search to keep payloads small

Skyscanner Travel APIs

  1. Apply before planning an integration. Keys go only to approved businesses with more than 100,000 monthly visits, after a commercial agreement on impact.com
  2. Don't plan bookings or payments through the API. It returns prices and links, and the traveller books on the airline's or agent's site
  3. Keep flight search creates under 100 a minute and car hire creates under 15 a minute, and stop on a 429 'Too many requests based on your rate limits'
  4. Don't cache, resell, repackage or redistribute results. The partner help centre says Skyscanner doesn't allow it

Questions

Which is better for AI agents, Booking.com Demand API or Skyscanner Travel APIs?

Booking.com Demand API scores 48.7 (D) on agent readiness against Skyscanner Travel APIs's 26.5 (F), and leads in 4 of 7 scored categories. Skyscanner Travel APIs leads on security & auth and payments & pricing.

Do Booking.com Demand API and Skyscanner Travel APIs need an API key?

Both need an API key.

Can an agent call Booking.com Demand API and Skyscanner Travel APIs without installing anything?

Yes. Booking.com Demand API has a hosted endpoint at https://demandapi-sandbox.booking.com/3.2 and Skyscanner Travel APIs at https://partners.api.skyscanner.net.

Other comparisons with Booking.com Demand API or Skyscanner Travel APIs

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.