Find Car Rental Locations

View all Booking.com Hotel & Travel Data endpoints →

Resolve a rental-location text query with optional language_code. Documentation describes downstream use of data.id, data.name, and data.coordinates.latitude/longitude for ID-, name-, or coordinate-based rental searches. Those are documented handoffs rather than observed live fields: this autocomplete response was not validated. Confirm airport, city, terminal, and country context before selecting pickup and return locations.

API Features

Rental pickup place discovery Evaluate location suggestions before constructing a rental quote request.
Documented ID handoff for car search Inspect data.id before setting pickUpId in the ID-oriented route.
Documented name handoff for rental locations Retain a selected data.name for the name-based rental search.
Rental coordinate provenance Verify coordinates and geographic context before setting pickup or return positions.

Live API Demo

GET /api/project/booking/car-auto-complete

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/booking/car-auto-complete?key=<API_KEY>&query=<query>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which suggestion values are used by rental searches?

Documentation points to id for pickUpId, name for location-name search, and coordinates for coordinate search. Inspect the actual response because this route was not live-validated.

Can a similarly named city location replace an airport pickup?

Do not assume equivalence. Confirm airport and geographic context before selecting locations and requesting rental candidates.

Related operations

Guides

View Subscription Plans →