Hotelbeds Hotel Booking API vs LetsFG

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.

LetsFG

Hosted MCP with OAuth 2.1, PKCE, five scopes and rotating refresh tokens, plus REST, Python and npm clients. Tickets are bought by a LetsFG booking agent after the hold, 4 to 11 minutes per the docs, and bookings can pause with questions.

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

LetsFG

1. Start on /v1/sandbox/ with no key; the booking states, questions and timings match production
2. After book_flight, poll get_flight_booking every 20 to 30 seconds and answer questions before expires_at_ms; an unanswered price change fails the booking and releases the hold
3. Honour retry_after_seconds on a 429. Over MCP the limit is 10 searches per 10 minutes and 100 a day, and early retries lengthen the pause
4. Fetch results with get_flight_results and the search_id rather than searching again, which spends allowance
5. Send the same idempotency_key when retrying a booking after a timeout
6. Treat a 410 as a retired route and read the replacement path in its body