Booking Get Property Details by Detail ID API

Retrieve documented property information with detail_id and optional stay dates, currency_code, and language_code. detail_id belongs to the properties workflow and is documented as coming from a detailId value; it is not interchangeable with numeric hotel_id. Accommodation autocomplete is unavailable, so use an independently known detail_id. This route was not live-validated; inspect returned property identity, stay dates, and price fields before enrichment.

API Features

Dedicated detail_id namespace Keep the property detail identifier separate from numeric hotel IDs and city UFIs.

Property-detail date inputs Supply check-in and check-out when inspecting a specific stay.

Independent detail identifier prerequisite Use a known detail_id instead of depending on unavailable accommodation suggestions.

Resolved property enrichment check Validate the actual identity and stay before joining detail data to a listing.

Live API Demo

GET /api/project/booking/properties-detail

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-detail?key=<API_KEY>&detail_id=<detail_id>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-detail?key=<API_KEY>&detail_id=<detail_id>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Evaluate enrichment of a known detail_id property record.
Check identifier provenance when migrating a property catalog.
Compare dated property information with the originally selected accommodation.
Detect accidental numeric-hotel-ID substitutions in property-detail requests.

Frequently asked questions

Can I use hotel_id=180769 as detail_id?

Do not assume that. detail_id uses the properties workflow's documented detailId namespace, with examples such as de/gold-palais, rather than the numeric hotel ID contract.

Where can I obtain a detail_id now?

Use an independently known, verified identifier. Accommodation autocomplete is unavailable, and this property-detail route was not live-validated.

Related operations

Guides

View Subscription Plans →