Get Stay Details by ID or URL
View all Booking.com Hotel & Travel Data endpoints →Inspect hotel details using query as a numeric hotel ID, a Booking.com property URL, or a supported hotel-name value. Optional dates, guests, rooms, currency, and display preferences describe the stay. Documentation supports these input forms, but this flexible lookup route was not live-validated and must not inherit the tested get-hotel-details schema by assumption. Accommodation autocomplete is unavailable; use an independently known property and verify the returned identity.
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/stays-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/stays-details?key=<API_KEY>&query=180769'
Query Result
Use Cases
- Evaluate hotel enrichment from a user-provided property link.
- Test numeric-ID and supported hotel-name resolution for the same property.
- Prototype a hotel lookup that retains the traveler's dates and guest counts.
- Detect wrong-property matches when accepting free-text hotel names.
Frequently asked questions
Which input forms are documented for query?
A numeric hotel ID, a full Booking.com property URL, or a supported hotel-name value. These forms were not live-validated on this route; verify the resulting property identity.
Can I assume a URL lookup returns the tested numeric-detail response?
No. Only get-hotel-details was validated for that hotel. Inspect the flexible route's actual schema, identity, and stay dates before relying on parity.