Recipe · Hotels API
Hotel search with RapidAPI
Live Booking.com rates with the filters the real site has (24 of them). Every property returns with a price, review score, room type, and a working booking link, so the agent can present a shortlist the user can act on immediately.
Free tier on RapidAPI. No card to try.
Step 1 · Connect
Call the listing host
The marketplace host is where the key comes from and where the usage meters. Same API, same request bodies; the only difference from our own domain is the host and the extra x-rapidapi-host header. Flights and hotels are separate listings with separate subscriptions.
curl -X POST "https://booking-live-api.p.rapidapi.com/search" \
-H "Content-Type: application/json" \
-H "x-rapidapi-host: booking-live-api.p.rapidapi.com" \
-H "x-rapidapi-key: $RAPIDAPI_KEY" \
-d '{"destination":"Lisbon","checkin_date":"2026-10-09","checkout_date":"2026-10-12"}'Bring your own RapidAPI key: every request is billed to your own subscription, never ours.
Step 2 · The job
The job
The job in plain words. In RapidAPI you express it as the configuration below instead of a prompt.
“Find me a hotel in Lisbon, October 9 to 12, 2 adults, review score 8+, free cancellation.”
Step 3 · Under the hood
The request
One POST, flat JSON in, flat JSON out. Field names are the ones in the OpenAPI spec.
POST https://booking-live-api.p.rapidapi.com/search
{
"destination": "Lisbon",
"checkin_date": "2026-10-09",
"checkout_date": "2026-10-12",
"adults": 2,
"filters": [
"review_score_8",
"free_cancellation"
]
}destination is required and takes free text. The field is not called location; sending location returns a 400 that says so.
Step 4 · Read the response
Fields your logic reads
The response is flat JSON. These are the fields this recipe branches on, with what each one means.
namestringThe property name as listed on Booking.com.
price_stringstringThe total rate for the stay as Booking.com displays it: “US$2,434”.
review_scorenumberBooking.com guest score out of 10.
review_countnumberHow many reviews the score rests on: a 9.1 from 12 reviews is not a 9.1 from 1,200.
room_typestringWhich room the rate belongs to: compare like with like across markets.
linkstring (URL)A working Booking.com link to the property.
Questions, answered plainly
- Is my key billed to me?
- Yes. The key is the one RapidAPI issued you, and usage meters against that subscription whichever host you call. There is no FlightPowers account and no second bill.
- Does this need a server of mine?
- No. It is one HTTPS request from whatever already runs your code. The OpenAPI spec is at flightpowers.com/openapi.json if you want to generate a client.
- What does it cost?
- The Booking.com Live API's free tier is 10 requests/month with a hard cap: enough to verify your key works, not to evaluate. The PRO plan is $10/month for 2,000 requests, and every plan includes every endpoint.
Also works with
Hotel search, elsewhere in your stack
More recipes
More to build in RapidAPI
One-way flight search
Flights API · search_oneway_flights
Round-trip search
Flights API · search_roundtrip_flights
Price-insights check
Flights API · search_oneway_flights
Cheapest-date scan
Flights API · search_oneway_flights
Rate-parity check
Hotels API · find_hotel_by_name
Fare-alert cron
Flights API · search_oneway_flights
Get live flight and hotel data
Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.
Free tier: 10 requests/month. No card to try.