WuBook MCP by usefulapi

WRITE: check in the guests of a reservation in ZaK. Applies to every guest of the reservation unless room_customer_ids is given. POST /kp/reservations/do_checkin.

WRITE: check out the guests of a reservation in ZaK. Applies to every guest of the reservation unless room_customer_ids is given. POST /kp/reservations/do_checkout.

WRITE: create a reservation in ZaK for one guest. Give rooms (room type and optionally the physical room id, with price and currency) and/or products (product id with price and currency). Set assign_rooms to let ZaK pick the physical rooms. This books inventory and is NOT idempotent: calling it twice creates two reservations, so check wubook_get_room_availability first and do not retry on an error without looking the reservation up. POST /kp/reservations/new.

One guest record by customer id (from a reservation's booker or room customers): name, country, address, contact, birth data, billing info. Personal data. Identity documents (type, number, expiry) are left out unless include_documents is true. POST /kp/customers/fetch_one.

The meaning of the short keys in prices and restrictions (p price, a availability, m MinStay, M MaxStay, c closure, ...). POST /kp/inventory/fetch_symbols.

Daily prices, availability and restrictions of one rate, starting at a date: for each product id a list with one object per day (p price, a availability, m/M min/max stay, c closed, ...; see wubook_get_inventory_symbols). POST /kp/inventory/fetch_rate_values.

One reservation by id or by reservation code (XY-0001): status, booker customer id, origin channel, board, dates, price split (rooms, extras, meals), payment, taxes and rooms with occupancy and customer ids. POST /kp/reservations/fetch_one_reservation.

Availability for a stay: for each room type id, the number of rooms available and the ids of the available physical rooms. The availability count can be lower than the number of listed physical rooms when a reservation has no physical room assigned yet; use the availability count when assessing bookable capacity. POST /kp/inventory/fetch_rooms_availability.

List the extras the property sells (id, name, price, VAT percentage, cost, tags). POST /kp/property/fetch_extras.

List the meal rules and meal prices per board type (fb, hb, bb, ai) for adults, teens, children and babies. POST /kp/property/fetch_meals_board.

List the products (a room type sold on a board basis: id, room type id, name, default price, occupancy). Product ids are the keys of prices and availability. POST /kp/property/fetch_products.

List the rates of the property (id, name, board, currency, standard flag). Use a rate id for prices and restrictions. POST /kp/property/fetch_rates.

List reservations, optionally filtered by creation, arrival or departure date ranges (inclusive). Newest first is not guaranteed; page with offset. Returns the page plus next_offset (null when the last page was reached). POST /kp/reservations/fetch_reservations.

List the room types (id, name, short name, default price, default occupancy). POST /kp/property/fetch_room_types.

List the physical rooms of the property (id, room type id, name, tags). POST /kp/property/fetch_rooms.

Reservations of the property for today (arrivals, departures and stays in house). POST /kp/reservations/fetch_today_reservations.

WRITE: revert the check-in of a reservation in ZaK. POST /kp/reservations/undo_checkin.

WRITE: revert the check-out of a reservation in ZaK. POST /kp/reservations/undo_checkout.

WRITE: overwrite daily prices, availability and stay restrictions of one rate. `products` maps a product id to a list of day objects; the first object is the day `from`, the next the following day, and so on. Only the fields you send per day change. Changes can be pushed to connected channels (OTAs) and affect live bookings, so confirm the values with the user first. POST /kp/inventory/write.