Search car rentals with different pickup and return locations
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Search for a car rental with separate pickup and drop-off locations. Supply pickUpPlaceId, pickUpLocationType, pickUpDate, pickUpTime, dropOffPlaceId, dropOffLocationType, dropOffDate, dropOffTime, and the required order string. Location IDs and location types come from rental-car location search results; include the corresponding airport code when a location is an AIRPORT. Optional inputs are driverAge, currencyCode, and page, whose documented default is 1. Dates use YYYY-MM-DD. The documentation also labels the time strings YYYY-MM-DD, so a usable time-of-day format is not established by the supplied evidence. No saved live probe covers this operation. A truncated documentation example shows a data.cars array with displayPricing.breakDown fields including basePrice, oneWayFee, payAtPickupPrice, payNowPrice, pricePerDay, totalPrice, and youngDriverFee; pickup and return location objects; fees; a price object; purchaseLink; and supplier address information. These are unverified example fields, not guaranteed live response fields. Fee fields may be null, which must not be treated as proof that a fee is zero. This is a search interface, not a booking or payment action, and it does not establish current availability.
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/tripadvisor-data/search-cars-different-drop-off API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-cars-different-drop-off?key=<API_KEY>&dropOffDate=<dropOffDate>&dropOffLocationType=<dropOffLocationType>&dropOffPlaceId=<dropOffPlaceId>&dropOffTime=<dropOffTime>&order=<order>&page=1&pickUpDate=<pickUpDate>&pickUpLocationType=<pickUpLocationType>&pickUpPlaceId=<pickUpPlaceId>&pickUpTime=<pickUpTime>'
Query Result
Use Cases
- Prototype an airport-to-another-city rental form with independent pickup and return location selections, while treating its offer display as unverified until tested.
- Prepare a road-trip route comparison that records both location IDs, rental dates, and supplied time strings without claiming that inventory is available.
- Preserve driver age, currency, sort input, and page while a traveler edits only the return location in a one-way rental search.
- Design a one-way cost panel around the documented price breakdown, with an explicit unknown state for nullable oneWayFee and youngDriverFee values.
Frequently asked questions
How do I specify different pickup and return locations?
Send separate pickUpPlaceId and dropOffPlaceId values, together with their respective location types. These values come from rental-car location search results. Both sets of location inputs are required.
When should I include the pickup or return airport code?
The documentation asks for the matching airport code when the selected location type is AIRPORT. The airport-code parameters are optional in the declared contract, but they provide the documented context for airport locations.
What date, time, and sort formats are documented?
pickUpDate and dropOffDate use YYYY-MM-DD. Both time parameters are required strings, but their documentation repeats that date pattern rather than establishing a time-of-day format. order is also required, with no allowed sort values supplied. Do not assume an invented time format or sort option is accepted.
Does a null oneWayFee mean the rental has no one-way charge?
No. oneWayFee appears as a nullable field in the documentation example, which is truncated and not verified by a live probe for this operation. Keep a null fee unknown rather than converting it to a zero charge.
Is the response verified, and can this request book a car?
No saved live probe covers this operation. The documentation example suggests data.cars with pricing, fee, location, supplier, and purchaseLink fields, but their live behavior is unverified. This GET request searches rental data; it does not reserve a vehicle or process a payment.