AllBookers Docs

Description

This endpoint updates the minStay value in the calendar for a specific room and rate plan. It receives roomId and ratePlanId as request parameters and a list of MinStayData objects in the request body.

For every date received, the method checks whether RoomAvailability already exists. If it exists, it updates or creates the related RateRoomAvailability entry for the selected rate plan. If it does not exist, it creates both RoomAvailability and RateRoomAvailability records.

At the end, all changed entities are saved and the derived price recalculation logic is triggered for the selected rate plan.

Endpoint

POST /updateCalendarMinStay

Parameters

Name	Type	Description
roomId	Long	The ID of the room whose availability calendar must be updated.
ratePlanId	Long	The ID of the rate plan that belongs to the room and whose minStay must be updated.

Request

Request parameters: roomId and ratePlanId. Content-Type: application/json

Authorization: Bearer <token>

Field	Type	Description
roomId	Long	Room identifier
ratePlanId	Long	Rate plan identifier
date	Date	Date to update
minStay	Integer	Minimum-stay value for that date
propertyName	String	Property name supplied in the payload

Request Body Example

POST /updateCalendarMinStay?roomId=12&ratePlanId=4
[
{"date": "2026-03-10T00:00:00.000+00:00", "minStay": 2, "propertyName": "Hotel Example"},
{"date": "2026-03-11T00:00:00.000+00:00", "minStay": 3, "propertyName": "Hotel Example"}
]

Process

The method first checks whether minStayDataList is null or empty.
If the list is empty, it sends an email about the Channel Manager problem and returns an error message.
It loads the room from the database using roomId.
If the room is not found, it sends a notification email and returns a room-not-found message.
It searches inside room.getRatePlans() for the rate plan with the given ratePlanId.
If the rate plan is not found, it returns a rate-plan-not-found message.
It converts all received dates into LocalDate values.
It loads existing RoomAvailability records for the room and those dates, including related rate data.
It builds a map by date so each calendar day can be processed efficiently.
For each MinStayData entry, it updates the existing RateRoomAvailability minStay value or creates a new RateRoomAvailability if missing.
If no RoomAvailability exists for that date, it creates a new RoomAvailability with default values and links a new RateRoomAvailability to it.
It saves all changed RoomAvailability records.
It saves all changed or newly created RateRoomAvailability records.
It triggers derivedPriceService.processRatePlanChange(ratePlanId, false).
It returns a success message when the operation completes.

Responses Returned

The method returns a plain String response. Depending on the situation, one of the following messages is returned:

Condition	Returned Response
minStayDataList is null or empty	minStay is received as empty list {roomId}
Room not found in database	Room with ID: {roomId} not exist in db, check room id {roomId} in allbookers
Rate plan not found for the room	Rate plan with ID: {ratePlanId} not found for room ID: {roomId}
Update completed successfully	minStay is successfully updated

Notes

The operation is executed within a single transactional context, ensuring that all database changes are committed together.
Date conversion depends on the server’s time zone, meaning the results may vary depending on the environment where the service is running.
When a new rate availability record is created, the price is initialized with a default value of zero.
Similarly, when a new room availability record is created, default values are assigned for total and occupied rooms, and the room is marked as open by default.
The pricing logic is also triggered during this process, even though the primary purpose of the operation is to update maximum stay values rather than prices.