Read Property Results from a Search URL

View all Booking.com Hotel & Travel Data endpoints →

Use this documented read-only POST with a user-provided Booking.com search-results url and optional page, currency_code, and language_code query parameters. The url remains a query input; no request-body field is exposed. Remove session and tracking values before sharing links, and review embedded dates and guests. This URL-import response was not live-validated; inspect which search conditions and pagination values are actually preserved.

API Features

Saved search URL import Evaluate structured property retrieval from a traveler-provided search-results link.
POST with query URL input Preserve the documented method and url query parameter instead of inventing a JSON body.
Page selection alongside imported context Inspect how page interacts with conditions embedded in the search URL.
Session-free link sharing Strip session and tracking information before putting URLs into reusable examples.

Live API Demo

POST /api/project/booking/properties-list-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-list-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

Should url be sent in a JSON request body?

No. This operation is POST but url is documented as a query parameter. Optional page, currency_code, and language_code are query inputs too.

Can I paste a full browser search link into shared examples?

Do not share session or tracking values. Sanitize the link and inspect embedded dates and occupancy. This URL-import route was not live-validated.

Related operations

Guides

View Subscription Plans →