Find Airport Transfer Places
View all Booking.com Hotel & Travel Data endpoints →Resolve a transfer pickup or drop-off text query with optional language_code. Documentation identifies googlePlaceId as the value for taxi-search pick_up_place_id and drop_off_place_id. This place-suggestion response was not live-validated. Confirm airport, hotel, entrance, and geographic context before constructing a transfer request; do not substitute a hotel ID or flight airport code for a place identifier.
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/taxi-auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/taxi-auto-complete?key=<API_KEY>&query=<query>'
Query Result
Use Cases
- Evaluate an airport-to-hotel transfer place selector.
- Disambiguate similarly named hotels before choosing a drop-off place.
- Inspect airport pickup suggestions before collecting a transfer time.
- Audit location-identifier provenance in a transfer-search prototype.
Frequently asked questions
What value should go into taxi-search place fields?
Documentation identifies googlePlaceId from this suggestion workflow. Inspect the actual selected suggestion before using it for pickup or drop-off.
Can I use an airport code or numeric hotel ID?
Do not substitute those identifiers. Taxi search requires the documented place-ID inputs, and this suggestion response was not live-validated.