Read Property Details from a URL
View all Booking.com Hotel & Travel Data endpoints →Evaluate a documented read-only POST using a Booking.com property url as a required query parameter. This endpoint exposes no separate date, occupancy, language, currency, or body input; inspect any context embedded in the URL and avoid sharing session or tracking values. Its live response and handling of dated or localized property links were not validated. Returned details do not create a reservation.
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/properties-detail-by-url API Response (JSON)
{} curl -X POST 'https://api.opendata-api.com/api/project/booking/properties-detail-by-url?key=<API_KEY>&url=<url>'
Query Result
Use Cases
- Evaluate a pasted hotel-link enrichment prototype.
- Inspect whether a saved dated property URL still describes the intended stay.
- Compare canonical and localized property links in a controlled integration test.
- Review imported hotel URLs for session data before retaining them in a shared catalog.
Frequently asked questions
Where do I pass dates and currency?
No separate fields are exposed on this operation. It accepts url as a query parameter; inspect any embedded URL context and the actual response.
Does the POST method mean this creates a reservation?
No. It is documented as a read-only property-details lookup. The route was not live-validated and does not promise a booking or payment result.