Length of stay (LOS)

As flexible as your prices are

With LOS you can defined every possible price structure you may have defined on your side since. For every possible checkin day, for every possible stay length, you can define the price as you want.

๐Ÿ“˜

LOS basics

  • LOS data contains prices and availabilities at the same time
  • For every possible checkin day you push the price for every possible length of stay (up to 62 nights) and occupancy (up to the max persons of the property)
  • To update an a price or availability inside a LOS, you need to push the entire LOS object, updates for single row is not possible.

How it works

  • The general concept is that each row in the LOS represents the availability and prices for one specific checkin day
  • The LOS object contains the possible check-in days (format: "YYYY-MM-DD")
  • Each check-in day has an array of objects
  • Check-in days for maximum 2 years can be pushed
  • Every object contains the currency of prices, the maximum amount of guests for which the rates are applicable and the prices according to lenght of stay

the length of stay object

ParameterTypeRequiredUsage
"los"objectYESObject of check in days
"los"."key"array of objectsYESEach possible check in day is represented by an array of objects.
"los"."key"[i]."currency" stringYESchoose from the list of supported currency parameters
"los"."key"[i]."guests"intYESthe number of guests for which the prices defined in this object are valid
"los"."key"[i]."price"array of numbersYESeach row contains the price for the according length of stay. When a row has value "0" this length of stay is not possible (for example row 1 represents the length of stay of 1 night, row 7 represents the length of stay 7 nights)
"los"."key"[i]."price"[i]."number"numberprice for the length of stay

Example

3 to 4 guests can check in on the 13th of September 2022 and stay from 4 to 7 nights, while 2 guests can stay only a minimum of 7 nights.

{
   "los": {
      "2024-05-01": [
         {
            "currency": "EUR",
            "guests": 2,
            "price": [
               0,   // Check-out not allowed on "2024-05-02"
               0,   // Check-out not allowed on "2024-05-03"
               0,   // Check-out not allowed on "2024-05-04"
              400,  // Check-out allowed on "2024-05-05" for this price
              500   // Check-out allowed on "2024-05-06" for this price
            ]
         },
         {
            "currency": "EUR",
            "guests": 3,  // Extra guest added
            "price": [
               0,   // Check-out not allowed on "2024-05-02"
               0,   // Check-out not allowed on "2024-05-03"
               0,   // Check-out not allowed on "2024-05-04"
              600,  // Check-out allowed on "2024-05-05"
              700   // Check-out allowed on "2024-05-06"
            ]
         }
      ]
   }
}

You can also find the recipe for a simple LOS here:

โ—

LOS do not work together with availabilities

Be aware that if you choose LOS we will not consider data sent to the endpoints RATES and AVAILABILITIES. The LOS contains both.