Booking Get Rental Collection Location API

Inspect documented collection-location information attached to 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

Collection place tied to the selected offer Inspect the supplier location using the original vehicle and search context.

Airport versus off-airport review Validate returned place information before labeling collection as terminal pickup.

Collection geography cross-check Compare actual location data with the pickup area intended by the traveler.

No route or shuttle guarantee Do not infer travel times or transfer arrangements from a location endpoint name.

Live API Demo

GET /api/project/booking/detail-supplier-location

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/detail-supplier-location?key=<API_KEY>&search_key=<search_key>&vehicle_id=<vehicle_id>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/detail-supplier-location?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.

Use Cases

Evaluate collection-location details for an arriving flight itinerary.
Check whether a rental candidate's pickup is actually at the intended airport area.
Compare selected supplier locations before a traveler chooses a vehicle.
Inspect actual location fields before designing a collection-point map.

Frequently asked questions

Does this guarantee pickup inside an airport terminal?

No. Inspect the actual collection-location response. The route name does not establish terminal access, shuttle availability, or travel time.

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 →