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

Duffel Flights and Stays API vs Hotelbeds Hotel Booking API

Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against Hotelbeds Hotel Booking API's 33.4 (F), and leads in every scored category. Both do hotel and stay search.

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

Which one, for what

Duffel Flights and Stays API BB

Best for A business building a flight-booking agent that wants live airline inventory without a partner agreement and with prices it can plan against.

Ahead on

  • Reliability, 80 against 33
  • Schema & documentation, 59 against 33
  • Agent ergonomics, 80 against 41
  • Security & auth, 60 against 38
  • Payments & pricing, 60 against 30
  • Maintenance & community, 92 against 3
  • Transparency & trust, 76 against 47

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

No OpenAPI document, llms.txt or official MCP server

Hotelbeds Hotel Booking API F

Best for A travel company with a Hotelbeds contract that wants wholesale rates behind its agent, and for prototyping hotel search without a sales call.

Also in its favour

  • Free to start without a card

Watch for

50 requests a day on evaluation, and the 51st returns a 403

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.

Maintenance & community Duffel Flights and Stays API +89

Duffel Flights and Stays API 92

Changelog entry on 14 October 2026 (deposit amounts on Stays bookings) and SDK 4.31.0 on 8 October (30). In the 90 days from 3 August, changelog entries on 28 September and 14 October and SDK releases 4.29.0, 4.29.1, 4.30.0, 4.30.1 and 4.31.0 (11 September to 8 October), counted half, 4.5 in all (20). Outside pull requests (#1192, #1196) merged in September, per the 1 October check, a public changelog and email support (20 of 25). The TypeScript SDK is current; the Python SDK is archived (12 of 15). CI on every push and pull request, Dependabot, and an October bump of three dependencies for CVEs (10). 30 + 20 + 20 + 12 + 10 = 92.

Hotelbeds Hotel Booking API 3

No changelog, release notes or dated API change found on the documentation index or the Booking API page, so we can't date the last change (0). No dated entries in the last 90 days (0). Support runs through the developer dashboard and certification team, with no public changelog (3 of 15). No official SDKs (0). No package to judge (0). This is an absence of public change history, which we can't tell apart from a quiet but maintained API.

Reliability Duffel Flights and Stays API +47

Duffel Flights and Stays API 80

incident.io status page at duffelstatus.com with per-supplier and per-product components and history (20). In the 90 days from 3 August, read from feed.atom on 1 November, 15 incidents (one of them a Scoot maintenance window) and two planned database maintenance windows. The feed holds 17 entries, the oldest on 4 August, and the status page's incident calendar shows that incident, the Chat assistant outage, starting on 3 August at 22:23 UTC, with nothing else posted that day. Each named one supplier, one product or one function, among them Air France KLM card payments on 17 August, saved cards failing on api.duffel.cards on 27 August, a Stays partial outage on 3 September, Sabre order errors on 3 September, the dashboard on 14 September, a Lufthansa Group, Qantas and Aegean search outage on 28 September and Travelport ticketing for a subset of carriers on 21 October. None took the core flights API down, and this run reads one supplier or product as partial whatever the label, so minor incidents only (20). Limit published, 60 requests per 60-second window, with ratelimit-* headers (15). 429 tells you to retry after ratelimit-reset, and order creation has explicit guidance (a 202 means processing, don't retry; use a 130-second timeout) (15). No SLA on the pricing page for either tier (0). Generally available (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

Hotelbeds Hotel Booking API 33

The docs link a public Pingdom report (stats.pingdom.com/lxdqh5mwxj3w) as the API status page. Its served page on 11 November is a 7-day overview frame (5 to 11 November) with no monitor names or components, filled in by script, not an incident page (10 of 20). No readable incident history (5). The evaluation quota is published, 50 requests a day, and production quotas aren't (8 of 15, an earlier partial value held). Going over the quota returns a 403 rather than a 429, and we found no backoff guidance. The hotels best-practices page says a 400 or a 500 shouldn't be resent unchanged and sets a 60-second minimum timeout for booking confirmation, which isn't overload handling. The API terms warn that excessive requests can get an account suspended (0). No SLA published (0). The Booking API is generally available (10). 10 + 5 + 8 + 0 + 0 + 10 = 33.

Agent ergonomics Duffel Flights and Stays API +39

Duffel Flights and Stays API 80

return_offers=false, supplier_timeout and max_connections size an offer request, and the offer list can be fetched separately (18 of 25). Cursor pagination with limit on list endpoints (20). Typed error codes with a documentation_url on every error (20). Retry rules for order creation are documented, but we found no idempotency key on order creation in the docs we read (12 of 20). Few required fields for a search. One maintained SDK (TypeScript); the Python SDK is archived (10 of 15). 18 + 20 + 20 + 12 + 10 = 80.

Hotelbeds Hotel Booking API 41

Availability takes stay dates and occupancy, and the Content and Cache APIs keep static hotel data out of the live calls, which cuts payloads. We didn't confirm field selection (15 of 25). Pagination not confirmed on the pages we read (8 of 20). No documented error codes found (5 of 20). Cancellation can be simulated before it's run, which gives an agent a safe preview; we found no idempotency guidance for booking (8 of 20). Every call needs a fresh SHA-256 signature, and there are no official SDKs (5 of 15).

Payments & pricing Duffel Flights and Stays API +30

Duffel Flights and Stays API 60

No x402, MPP or L402 (0). Per-unit prices published without login, re-read on 1 November, $3.00 per order, 1 per cent for Managed Content, $2.00 per paid ancillary, 2 per cent FX, $0.005 per search above 1,500 to 1 (20). Sign-up is free and test mode needs no card or contract, per the 30 September check (20). A person signs up in the dashboard to get tokens (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Hotelbeds Hotel Booking API 30

No x402, MPP or L402 (0). No published price list; live rates are under a commercial contract (0). Registration gives a free evaluation key with no card (20). A person registers in a browser and passes certification with Hotelbeds staff before going live (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Duffel Flights and Stays API +29

Duffel Flights and Stays API 76

Closed service with a public services agreement under the law of England and Wales (15). Privacy policy names Duffel Technology Limited (company 11188295) as controller, updated 17 June 2026, with a DPA addendum referenced from the services agreement. Retention is "as long as reasonably necessary" with no periods (18 of 30). A versioning policy keeps the previous version 6 months after a new one and promises email notice before breaking changes; v1 ended on 23 January 2025 (20). The security page says Duffel runs entirely on Google Cloud. Transfers are described in general terms and we didn't find a subprocessor list (10 of 20). 15 + 18 + 20 + 10 = 63. The privacy policy and services agreement rest on the 1 October check.

Hotelbeds Hotel Booking API 47

Closed service with public API terms of use, governed by Spanish law with the courts of Palma de Mallorca (15 of 30). The group privacy policy on www.hbxgroup.com can't be read. That host answered its robots.txt with a 403 bot check on 11 November, so the 30 September reading is struck. The API terms' personal-data clause requires security measures, use only for evaluating the transaction and return or destruction at the end, and the terms make all information under the agreement confidential, with no DPA or retention periods for API data (5 of 30). No deprecation policy or dated notices (0). No subprocessor list or data locations found on the pages we can read (0). 15 + 5 + 0 + 0 = 20.

Schema & documentation Duffel Flights and Stays API +26

Duffel Flights and Stays API 59

No public OpenAPI document found (0). duffel.com/llms.txt and duffel.com/docs/llms.txt both return 404, re-checked on 1 November (0). The API reference states what each endpoint does and the guides cover when to use offer requests, partial offer requests and holds (16 of 20). Typed fields with enums such as cabin_class and passenger type, required fields marked (13 of 15). An error object with type, code, title, message and documentation_url, seven error types and per-status guidance for order creation (15). Duffel-Version header, a written versioning policy and a public changelog (15). 0 + 0 + 16 + 13 + 15 + 15 = 59.

Hotelbeds Hotel Booking API 33

No published contract we can read. The getting-started page names a Swagger specification and Postman collections with no download link (the Postman button is drawn by script), and the API Reference page draws an OpenAPI 3.0 file with Redoc in the browser. A file only page script fetches isn't a published contract here, so it wasn't requested (0). No llms.txt or Markdown docs for agents (0). The Booking API pages explain the flow (availability, CheckRate when a rate needs rechecking, then bookings) and say BookingAPI prices are final (14 of 20). The workflow page's request and response examples show field names and value formats, with no types, enums or required flags written out (4 of 15). Postman and curl examples; the hotels best-practices page says what a 400 and a 500 mean and what to do, and points to an API errors page that the hotels section doesn't have (10 of 15). The version sits in the path (/hotel-api/1.0) and we found no changelog or release notes in the documentation menu (5 of 15, an earlier partial value held). 0 + 0 + 14 + 4 + 10 + 5 = 33.

Score by category

CategoryWeightDuffel Flights and Stays APIHotelbeds Hotel Booking APIEdge
Reliability16%8033Duffel Flights and Stays API +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5933Duffel Flights and Stays API +26
Agent ergonomics13%8041Duffel Flights and Stays API +39
Security & auth14%6038Duffel Flights and Stays API +22
Payments & pricing10%6030Duffel Flights and Stays API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%923Duffel Flights and Stays API +89
Transparency & trust7%7647Duffel Flights and Stays API +29
Negative events≤1500
TotalBB 71.3/100F 33.4/100

Facts side by side

FactDuffel Flights and Stays APIHotelbeds Hotel Booking API
KindHTTP APIHTTP API
VendorDuffelHotelbeds (HBX Group)
Hosted endpointhttps://api.duffel.comhttps://api.test.hotelbeds.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per useYour plan
x402nono
LicenceMIT (SDK)none
Read-only variant documentednono
llms.txtnono
Last release2026-10-14none
Terms last updated2026-06-17no date given
Privacy policy last updated2026-06-17no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity55 stars, 87k npm/wknone
Agent reviews4/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Duffel Flights and Stays API higher.

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

Duffel Flights and Stays API

Self-serve sign-up and test mode need no card or contract, prices are published per order and per excess search, and every status incident since 3 August touched one supplier or product. There is no OpenAPI document, llms.txt or official MCP server, and the default limit is 60 requests a minute.

Hotelbeds Hotel Booking API

Free evaluation key on registration, no card and no sales call. 50 requests a day on evaluation, and the 51st returns a 403.

Before you call either

Duffel Flights and Stays API

  1. Send Duffel-Version: v2 on every request or you get a version error
  2. Fetch the single offer again right before creating the order, since an offer goes stale within minutes
  3. Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
  4. Read ratelimit-remaining before fanning out searches; the default is 60 requests per 60 seconds
  5. Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you

Hotelbeds Hotel Booking API

  1. Compute X-Signature fresh per request from key, secret and the current epoch seconds, in that order
  2. Budget the 50 daily evaluation calls; cache hotel content and only call availability for real dates
  3. Run CheckRate on a rate before booking when the availability response says it needs rechecking
  4. Read a 403 on the test host as the daily quota first, not a bad key
  5. Simulate a cancellation before running it

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Duffel Flights and Stays API or Hotelbeds Hotel Booking API?

Duffel Flights and Stays API scores 71.3 (BB) on agent readiness against Hotelbeds Hotel Booking API's 33.4 (F), and leads in every scored category.

Do Duffel Flights and Stays API and Hotelbeds Hotel Booking API need an API key?

Both need an API key.

Can an agent call Duffel Flights and Stays API and Hotelbeds Hotel Booking API without installing anything?

Yes. Duffel Flights and Stays API has a hosted endpoint at https://api.duffel.com and Hotelbeds Hotel Booking API at https://api.test.hotelbeds.com.

Other comparisons with Duffel Flights and Stays API or Hotelbeds Hotel Booking API

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.