Booking Get Rental Supplier Information API

Inspect documented supplier information attached to a selected vehicle offer 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

Supplier attached to a vehicle context Request supplier information for a concrete selected rental offer.

No company-name-only lookup Retain vehicle_id and search_key instead of guessing a supplier identifier.

Supplier metadata field inspection Validate actual business information before presenting it to travelers.

Offer-specific supplier comparison Keep supplier observations connected to the search that produced each candidate.

Live API Demo

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

API Response (JSON)

{}

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

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

Use Cases

Evaluate a supplier-information panel for a selected car offer.
Inspect supplier metadata before retaining a low-price corporate-travel candidate.
Compare supplier-field coverage across two shortlisted vehicle contexts.
Audit whether rental candidates resolve to the expected supplier identity.

Frequently asked questions

Can I search a rental company by name here?

No company-name input is exposed. This route requires a vehicle_id and search_key from a rental search.

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 →