Search Rentals by Pickup ID

View all Booking.com Hotel & Travel Data endpoints →

Search the documented rental workflow with pickUpId from car location autocomplete and required pickup/return dates and times. Optional driver_age, transmission, hasAirConditioning, and language_code refine the request. Do not replace pickUpId with an airport code, hotel ID, or manually guessed value. This ID-oriented search response and its relationship to coordinate-based rental results were not live-validated.

API Features

Autocomplete pickup ID input Use the documented data.id from car location discovery.
ID-search interval completeness Supply pickup and drop-off date/time values for an intentional rental duration.
Rental ID filter subset Use only the preferences exposed by this endpoint rather than importing every coordinate-search input.
Pickup identifier kept opaque Retain the selected location ID without substituting a different identifier family.

Live API Demo

GET /api/project/booking/search-by-id

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/search-by-id?key=<API_KEY>&drop_off_date=<drop_off_date>&drop_off_time=10%3A00&pickUpId=<pickUpId>&pick_up_date=<pick_up_date>&pick_up_time=10%3A00'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Is pickUpId an airport IATA code?

Documentation describes it as the id returned by car-auto-complete. Do not replace that value with a flight airport code or a hotel identifier.

Can I pass all coordinate-search filters here?

No. This endpoint exposes a narrower set of parameters. Preserve its documented inputs and inspect its actual response; the route was not live-validated.

Related operations

Guides

View Subscription Plans →