Recipe · Hotels API
Rate-parity check with RapidAPI
Identical calls except price_as_seen_from (the REST field is proxy_country), a two-letter code that prices the stay as a shopper in that country would see it. Ask each market more than once: in a controlled run on 2026-08-28, Germany and Japan answered with the same number every time while the US market moved between identical requests. The agent compares the ranges and calls a gap real only when one market’s whole range sits below the other’s.
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.
“Price the Rixos Sungate in Antalya for Oct 5–10 as seen from Germany and from Japan. Ask each market three times.”
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/hotel_by_name
{
"hotel_name": "Rixos Sungate Antalya",
"checkin_date": "2026-10-05",
"checkout_date": "2026-10-10",
"proxy_country": "de"
}proxy_country is an input, never a response field. Hold one named property fixed and sample each market several times back to back: rates move between identical calls, so a single reading per country measures the noise as much as the market.
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.
availablebooleanFalse means sold out for the dates: the response keeps the same shape with nulls, so parsing never branches on an error format.
price_stringstringThe total rate for the stay as Booking.com displays it: “US$2,434”.
pricenumberThe same rate as a plain number, for comparing quotes across markets or dates.
room_typestringWhich room the rate belongs to: compare like with like across markets.
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
Rate-parity check, 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
Hotel search
Hotels API · search_hotels
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.