Inspect Rental Offer Packages
View all Booking.com Hotel & Travel Data endpoints →Inspect documented package choices associated with a selected rental vehicle 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/detail-packages API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/detail-packages?key=<API_KEY>&search_key=<search_key>&vehicle_id=<vehicle_id>'
Query Result
Use Cases
- Evaluate package-choice information for a selected rental candidate.
- Compare documented package conditions within one vehicle offer.
- Inspect the package schema before designing an upgrade comparison panel.
- Check whether package responses support the intended corporate-travel review step.
Frequently asked questions
Can I assume packages include insurance details?
No package fields were live-validated. Inspect what the response actually supplies before labeling coverage, deposits, or upgrades.
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.