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
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/car-auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/car-auto-complete?key=<API_KEY>&query=<query>'
Query Result
Use Cases
- Evaluate an airport-versus-downtown rental pickup selector.
- Disambiguate rental locations before collecting pickup and return times.
- Inspect location identifiers for a documented ID-based rental workflow.
- Validate candidate coordinates for a same-location or one-way rental search.
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.