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
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-list-by-url API Response (JSON)
{} curl -X POST 'https://api.opendata-api.com/api/project/booking/properties-list-by-url?key=<API_KEY>&url=<url>'
Query Result
Use Cases
- Evaluate structured import of a traveler's saved accommodation search.
- Audit which dates and guest settings survive search-URL ingestion.
- Compare the first and subsequent imported search pages in a bounded test.
- Review old search links for expired dates before using them for current research.
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.