Get a Rental Vehicle Offer

View all Booking.com Hotel & Travel Data endpoints →

Inspect documented vehicle specifications and offer context using required search_key and vehicle_id, with optional currency_code, language_code, and unit. Obtain both required values from the same rental search; search_key is opaque offer context, not an account login. No captured key is supplied as a default. This dedicated response and token lifetime were not live-validated, so inspect actual fields before product use.

API Features

Vehicle and search paired input Use vehicle_id and search_key from the same rental result.
Selected vehicle specification review Inspect actual vehicle fields before displaying specifications.
Vehicle-detail units preference Choose the documented unit value without altering the rental search context.
Offer context without rental commitment This vehicle read does not reserve a car or guarantee a quote.

Live API Demo

GET /api/project/booking/vehicle-details

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/vehicle-details?key=<API_KEY>&search_key=<search_key>&vehicle_id=<vehicle_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Can vehicle_id be used without search_key?

No. Both are required. Documentation derives vehicle_id from v_id in a rental search and search_key from that same search context.

Where do the required offer-context inputs come from?

Documentation identifies data.search_key and search_results.vehicle_info.v_id in rental search. Keep them paired, handle the key privately, and obtain a new search context when necessary; no lifetime guarantee was validated.

Related operations

Guides

View Subscription Plans →