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

Property-link detail entry Evaluate a user-provided Booking.com hotel link without extracting a numeric ID first.
Only the URL is an input Do not invent separate stay, currency, locale, or body parameters for this route.
Embedded-link context review Check how dates and locale carried in a URL affect the actual result.
Read-only POST semantics The documented detail lookup does not submit a hotel booking.

Live API Demo

POST /api/project/booking/properties-detail-by-url

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X POST 'https://api.opendata-api.com/api/project/booking/properties-detail-by-url?key=<API_KEY>&url=<url>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →