How Newbookclloud talks to your Wubook
Every module in the catalogue talks to your Wubook property through the official Wubook API — using the authorisation token you issue via Wubook Login. Below is the technical reference for the five endpoint families we use, and which module needs which scope.
The five Wubook endpoint families we call
1. Rates endpoint
Reads current BAR, derived rates, corporate rates and rate-plan structure. Writes new BAR overrides within the min/max bounds you configure. Used by: Channel Autopricer, Corporate Rate Manager. Scope: "Read + Write Rate Plans".
2. Availability endpoint
Reads inventory levels per date and room type. Writes temporary blocks for group enquiries. Used by: Group Enquiry Router, Wubook Sync Sentinel. Scope: "Read + Write Availability".
3. Reservations endpoint
Reads reservation records including guest first name and surname, arrival, departure, room, channel of origin, special requests. Never writes to this endpoint — reservations remain authoritative in Wubook. Used by: Arrivals Digest, OTA Reconciliation, Nightly Trial Balance, Data Warehouse Bridge, Guest Wi-Fi Sign-On. Scope: "Read Reservations".
4. Guest and Charges endpoints
Reads folio structure. Writes new charge lines to folios (for F&B extras). Reads all posted charges for reconciliation. Used by: F&B POS Bridge, Wubook to Fatture in Cloud Bridge, Nightly Trial Balance. Scope: "Read Guest + Read/Write Charges".
5. Channel and Room States endpoints
Reads channel connection status and sync lag. Reads and writes room housekeeping states. Used by: Wubook Sync Sentinel (read-only), Housekeeping Board (read/write). Scope: "Read Channel + Read/Write Room States".
Rate limits and polling cadence
Wubook publishes a soft rate limit of 60 requests per minute per token, with burst allowance up to 120. Our modules poll on cadences well below this ceiling — the fastest is Sync Sentinel at 45 seconds, still less than 2 requests per minute per property. In aggregate a typical hotel with 5 modules active consumes about 8 requests per minute.
What happens when the Wubook API is down
Every module runs a local buffer of the last successful read and gracefully degrades — for example, Arrivals Digest ships from cache if the 06:30 fetch fails, while Autopricer skips the night. Sync Sentinel deliberately alerts on any Wubook-side failure so you know immediately.
Adding new integrations
If you would like Newbookclloud to build a module that connects Wubook to a system we do not currently support, write to marco@newbookclloud.org. Typical lead time from validated request to shipped module is 6 to 10 weeks.