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

Transfer pickup and drop-off discovery Evaluate place suggestions for each end of an airport transfer.
Documented googlePlaceId handoff Inspect actual place identifiers before constructing taxi-search inputs.
Entrance and airport ambiguity review Verify the intended pickup point rather than selecting by name alone.
Transfer-specific location namespace Keep place identifiers separate from hotel IDs and airport IATA codes.

Live API Demo

GET /api/project/booking/taxi-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/taxi-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

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.

Related operations

Guides

View Subscription Plans →