Set SiteMinder minimum stay and closed to arrival for peak dates

1. Go to Distribution > Inventory, open the room rate's connections drop-down and click Rates next to a channel rate; switch the drop-down to Closed to arrival or Min length of stay.
2. Tick the CTA box or type the Min Stay value for each date, then Save. For many dates use Bulk update and pick the restriction in the Set drop-down.
3. A dash instead of a checkbox means that channel rate does not take the restriction. Note which channels showed a dash and set the restriction in each one's own extranet.
4. Check Rooms and rates > Rate plans as well: the Default minimum stay there covers only new dates, so the holiday dates already loaded keep their old value.
5. After the holidays, go back to each channel rate and untick CTA or set Min Stay back to 1. A forgotten restriction keeps blocking short bookings in January.

For Christmas, close all room rates to arrivals on 24 and 25 December and set a 3-night minimum stay from 23 to 27 December on every channel that supports it.

1. 01

   Check support per channel first

   list_channels shows, for every channel rate, which restrictions SiteMinder can send. The agent splits your request into what SiteMinder can deliver and what has to be set in the channel extranet, before it touches a date.

2. 02

   Pick the room rates that sell

   From list_room_rates the agent takes the base rates mapped to at least one enabled channel. It asks before restricting a long-stay or package rate, since a 3-night minimum on a weekly rate makes no sense.

3. 03

   Set CTA and minimum stay in one pass

   One update_restrictions call per date block carries both values, for example cta on 24 and 25 December and min_los 3 from 23 to 27 December. Each call waits for your OK with the dates and channels listed.

4. 04

   Report what SiteMinder skipped

   The response lists channel rates that did not take a restriction. The agent turns that into a to-do: which channel, which dates, which restriction to set in its extranet.

5. 05

   Schedule the lift

   If you ask, the agent notes the end date and on 28 December clears CTA and resets min_los to 1, the value SiteMinder uses for no minimum. If the closure was a stop sell made with close_dates, it removes that too.

Christmas restrictions, 23 to 27 Dec
CTA on 24 and 25 Dec: Booking.com, Expedia, Direct Booking (6 room rates)
Min stay 3 nights, 23 to 27 Dec: Booking.com, Expedia, Agoda, Direct Booking
Not supported, set in the extranet yourself: CTA on Agoda (2 room rates)
Skipped on purpose: Weekly Saver rate (long stay)
Reminder set: lift on 28 Dec

• SiteMinder can send a restriction only where Data supported by this channel rate lists it, under Distribution > Channels > Edit room rates mapping > Configure; the rest must be set in the channel's extranet.
• Default minimum stay, default maximum stay and release period on a SiteMinder rate plan apply only to new rate plans and future dates, so existing dates need date-specific restrictions.
• SiteMinder treats availability 0 and stop sell differently: availability 0 closes a room type and all its rates on every channel, while a stop sell closes one rate or channel and leaves the rest selling.
• An Automatic closure yield rule in SiteMinder watches the availability of one room type or rate, not the total for the property, and deleting the rule reopens the affected rates.
• If a connected PMS, RMS or CRS syncs restrictions, SiteMinder overwrites manual CTA, minimum stay and stop sell changes with the values from that system.

update_restrictions and close_dates ask for your OK by default. To run it on a schedule without you, switch confirmation off for those tools in your dashboard.

Sources: SiteMinder Help: set up and manage restrictions · SiteMinder Help: add or remove stop sells · SiteMinder Help: set up an automatic closure yield rule · SiteMinder Help: minimum and maximum length of stay restrictions

curl https://cotlet.dev/api/v1/siteminder/update_restrictions \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"room_rate_ids":["rr_48213","rr_48210"],"from":"2026-12-24","to":"2026-12-25","restrictions":{"cta":true,"min_los":3}}'

{
  "status": "updated",
  "room_rates": 2,
  "dates": 3,
  "channels": [
    "Booking.com",
    "Expedia",
    "Direct Booking"
  ],
  "skipped": [
    {
      "channel": "Agoda",
      "reason": "CTA not supported by this channel rate"
    }
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is siteminder_update_restrictions. Example data.

• Update SiteMinder rates for busy dates and events
• Fill SiteMinder gap nights by lowering minimum stay
• Weekly SiteMinder channel performance and pace report
• SiteMinder API and MCP server: every tool
• All use cases