The inventory endpoints let you maintain a local copy of Booking.com's accommodation-property inventory: the properties available to book, together with their static content such as names, locations, ratings, policies, images, and booking links.
The inventory is served by the List accommodation properties endpoint (POST /inventory/properties), which streams the properties as newline-delimited JSON (NDJSON). See the API Reference for the request parameters, response schema, and streaming protocol.
The endpoint is designed to back a local database that you refresh incrementally, rather than re-download in full each time:
- Seed a full copy. Request the endpoint without
updated_sinceto receive the complete inventory. A full sync is a large transfer, so run it infrequently, for example once a month. - Apply incremental updates. On a regular cadence, for example daily, request the endpoint with
updated_sinceset to the timestamp of your previous sync. Only properties changed at or after that instant are returned. Upsert each returned record into your local copy.
Because updated_since filters on the last change to each property record, an incremental sync returns only what has changed since the previous run, which keeps the daily transfer small while your local copy stays current.