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
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/vehicle-details 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>'
Query Result
Use Cases
- Evaluate a specification panel for a selected rental vehicle.
- Compare two shortlisted vehicles using their original search context.
- Check the actual vehicle response before adding luggage or seat labels.
- Audit vehicle-ID and search-key mismatches in rental integration tests.
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.