Search Rentals by Pickup Coordinates
View all Booking.com Hotel & Travel Data endpoints →Search documented rentals with required pickup and drop-off coordinates, dates, and times. Driver age is documented as 30 to 65; optional transmission, supplier, car_type, air conditioning, language, and sort refine the request. Documentation identifies data.search_key and search_results.vehicle_info.v_id for later vehicle reads, plus returned filter identifiers. Rental results, prices, location handling, and all follow-up routes were not live-validated.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/search-car-rentals API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/search-car-rentals?key=<API_KEY>&drop_off_date=<drop_off_date>&drop_off_latitude=40.6917&drop_off_longitude=-74.1801&drop_off_time=10%3A00&pick_up_date=<pick_up_date>&pick_up_latitude=40.6917&pick_up_longitude=-74.1801&pick_up_time=10%3A00'
Query Result
Use Cases
- Evaluate rental discovery for an airport pickup and a separate return point.
- Compare documented transmission preferences for a fixed rental interval.
- Inspect SUV or people-carrier filters for a group-travel prototype.
- Carry selected vehicle and search context into detail inspection rather than guessing vehicle identifiers.
Frequently asked questions
What inputs are required for coordinate-based rental search?
Both pickup and drop-off latitude/longitude, dates, and times are required. Verify the actual locations and use the documented driver-age range of 30 to 65.
What should I retain for vehicle details?
Documentation points to data.search_key and a selected search_results.vehicle_info.v_id. Keep them from the same search; live response and quote semantics were not validated.