Booking Car Rentals Scraper
Pricing
from $1.60 / 1,000 car rental chargeds
Booking Car Rentals Scraper
Get car rental search results from Booking. Talks directly to Booking.com's own mobile app API, no login or API key needed. Split from the mature, published booking-all-in-one-api for a focused, single-purpose workflow.
What does Booking.com Car Rentals Scraper do?
Booking.com Car Rentals Scraper searches Booking.com car rentals by pickup location and dates, with real supplier/price/rating data — confirmed live: a real Los Angeles search returned 396 real listings. Free-text pickup locations are resolved to coordinates automatically. Optionally fetches full car detail (specs, what's included, cancellation terms) for every result in one run.
It talks directly to the same internal API the official Booking.com Android app uses, reverse-engineered by capturing live traffic from a real device — car rentals is a genuinely separate backend from hotels, confirmed live by opening the app's own Car rentals tab. No Booking.com account, no API key of your own. This is the car-rentals slice of Booking.com All-in-One API, split out as its own focused Actor.
Why use Booking.com Car Rentals Scraper?
- Real results, confirmed live — 396 real cars with real supplier names, per-rental prices, and ratings for a real Los Angeles search
- Automatic location resolution — pass a plain city name; this Actor resolves it to coordinates for you
- Optional full car detail in the same run — specs, what's included, cancellation terms, no separate Actor call needed
- The same
searchKeyworks for every car in a search — confirmed live, so detail fetches don't need per-vehicle re-derivation - No account needed — every request works fully anonymously
- Use cases: car rental price monitoring, travel search products, supplier comparison
Input
| Field | Type | Description |
|---|---|---|
locationQuery | string | Free-text pickup location, e.g. Los Angeles. If lat/lng aren't also given, this Actor only looks up matching locations and pushes them (no search). If lat/lng are missing, this is used to auto-resolve them. |
location | string | Pickup location name, used with lat/lng. Auto-filled when resolving from locationQuery. |
lat / lng | number | Pickup coordinates. Skips locationQuery resolution. |
pickup / dropoff | string (ISO 8601) | Pickup/drop-off datetime, e.g. 2026-09-24T10:00:00.000Z. |
driverAge | integer | Default 30 |
currency | string | Default HOTEL (account currency). Confirmed live to change returned prices. |
includeDetail | boolean | Fetch full specs/inclusions/cancellation-terms detail per car. Default false. |
maxItems | integer | Stop once this many cars have been pushed. Default: push every result from the search. |
Example (search):
{"locationQuery": "Los Angeles","pickup": "2026-09-24T10:00:00.000Z","dropoff": "2026-09-27T10:00:00.000Z","currency": "USD","maxItems": 20}
Example (location lookup only):
{ "locationQuery": "Los Angeles" }
Output
One dataset row per car (trimmed example):
{"title": "Nissan Rogue","subtitle": "or similar SUV","supplier": { "name": "Alamo", "rating": { "score": "9.1", "description": "Superb" } },"pricing": { "finalPriceDisplay": "US$233", "durationText": "Price for 3 days" },"metadata": { "vehicleId": "790637691" },"detail": { "...": "full specs/inclusions/cancellation terms, only present when includeDetail is true" }}
Known limitations
- Location resolution takes the first suggestion with coordinates. For an ambiguous
locationQuery, run a lookup first and pass exactlat/lnginstead. - Availability is genuinely route/date-dependent. Some pickup points (e.g. airports with limited standing inventory, or dates too close to now) can legitimately return zero cars — a real availability constraint, not a bug.
- This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Booking.com B.V. Behavior may change if Booking.com changes its API.
Pricing
Pay-per-event: $0.0025 per car-rental result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Location suggestion lookups are not charged.