Start free

Help centre

Public availability calendar (for the property's website)

A calendar guests can open or that the property embeds on its own website. It shows which days are free; it never shows guest details. Guests can't book through it, but if the property allows it they can send a booking request (below).

Setting it up

Owner/admin: Website calendar (menu) → Calendars for your website.

How far ahead — Calendars show ahead, above the calendars: one setting for the whole property (1–24 months, 12 to start with). It applies to every calendar of the property and to the calendar beside the booking list. The calendar shows that many months from today, to the end of that week. Guests can send requests only for stays that start within it (they may end after it). Staff can enter bookings for any dates. Press Save next to it.

Language — the calendar and its request form speak 31 languages (all EU languages, Norwegian, Russian, Ukrainian, Turkish, Chinese, Japanese and Korean). They use the language of the website page they're on; if the page doesn't say or uses another language, the guest's browser language; if that isn't one of them either, Default language (below Calendars show ahead; new properties start with the language you use the app in). Room and property names stay as you wrote them — write them in the language most of your guests read, or in English.

Each property has one or more calendars, listed by name with their room and where they were last seen. Every property starts with one (guests choose the room). Tap a calendar to open it — it has three parts, Settings, Put it on your website and Delete this calendar:

  1. Name: only for you, to tell calendars apart — e.g. where its code is pasted ("topu.ee/kalender").
  2. Room: one room, or "Guest chooses" (a dropdown above the calendar). Press Save.
  3. Put it on your website: choose the kind of code (tabs) and Copy. The Language is normally "Same as the website": the script then shows the calendar in the language of the page it's on, so one calendar serves every language version of the website. A link can't know the page's language and uses the guest's browser language (else Default language) — pick a language there to fix it. Kinds of code:
    • Script — paste it into the website where the calendar should appear. It fits the page's width and its own height, and the booking-request form opens over the website.
    • Link — for a "check availability" button or link. If the website builder doesn't allow scripts, put the link in its embed box or an iframe (<iframe src="…link…" style="width:100%;height:640px;border:0"></iframe>); the calendar then has a fixed height and scrolls inside it.
  4. The Preview shows the result; Open in a new tab opens it in a new tab.

The script code's link to BookMeAPillow.com must stay as it is and visible — it's the condition for using the calendar. If it's changed (other text, rel="nofollow" or anything else added), hidden or removed, the calendar shows "To the website owner: the “BookMeAPillow.com” link in this calendar’s code has been changed, hidden or removed. Keeping it as it is, visible, is the condition for using the calendar — please paste the code unchanged (in the app: Website calendar)." at its end; it disappears once the code is pasted unchanged again.

Changing a calendar's settings changes it on the website the next time it loads — the code stays the same, so nothing needs to be done on the website. New bookings and changes to rooms, and nights read from calendar links, appear there the next time it loads too: the calendar is kept ready so it loads fast for every guest, and anything changed in the app makes it fresh. Only things nobody changes take a minute or two: a hold running out, or a new day starting. A booking request is always checked against the latest bookings when staff confirm it. Under each calendar's name the app shows where it was last seen ("Last seen on …, …"), so you can tell which calendar is on which website. The browser usually reports only the site, not the exact page.

Add calendar (next to the heading): type a name and add another calendar (e.g. one per room, on different pages). Delete this calendar removes a calendar: every website using its code then shows only a link instead — the app warns first and shows where it was last seen.

The first kind of link, …/widget/<property>?room=… (given out by Settings only in late October 2026), no longer works: it shows "This calendar doesn't exist.". Use a calendar's code from Settings instead.

What guests see

The calendar starts straight with the days (with several rooms, the room choice above them). Free days are the only strongly coloured ones, so guests find them at once; a small legend at the end names the three looks:

  • Available (green): free.
  • Not available (grey): booked, or already past — either way it can't be booked.
  • Awaiting confirmation (soft amber): held by an unconfirmed booking; may become free if the hold lapses.

Everything else is explained in a small dark bubble at the day itself — when the mouse is over it on a computer, when it's tapped on a phone — so guests see it wherever they are in a long calendar, also on a website using the script code:

  • A day's date and look; on amber days "May become free after …" with the day the hold runs out (not the exact time); "Guests arriving during the day" and "Previous guests leaving" where relevant.
  • Hovering shows a thin outline around the day; days don't move.
  • Waiting-list and cancelled bookings don't make a day look booked.
  • Identical rooms booked as one show as booked only when all of them are taken.

For AI assistants and other tools

Each calendar can also be read as data (JSON), for AI assistants, scripts and other tools that can't run the calendar itself. Nothing needs setting up: it follows the calendar's settings.

  • https://bookmeapillow.com/api/v1/property/<property id> lists all of the property's room types, each with a link to its free periods — the same address for every calendar of the property, so an assistant gets the whole picture whichever calendar page it finds.
  • Each room's link lists its free periods from today as far ahead as the calendar shows: arrival on or after checkIn, departure on or before checkOut. Days that are taken or temporarily booked are simply not listed. No guest details, ever.
  • Like the calendar, it catches up with new bookings within a couple of minutes.
  • The script code from Settings (since 7 November 2026) already links to that address, in a part only tools that don't run JavaScript see, so AI assistants reading the website find it on their own. Code pasted earlier keeps working; to add the link, paste the calendar's code again.

Booking requests

Owner/admin: Website calendar → Booking requests: turn on Let guests send requests and optionally add a Privacy notice link. The e-mails go to the property's Notification e-mails (Settings; up to 5 addresses, they needn't be staff of the app). From then on every calendar of the property takes requests — links and embed codes already in use included; nothing needs changing on the website.

The guest taps the arrival day, then the departure day. When the first free day comes into view, a balloon points at it once: "Tap a free day to choose your arrival.". It fades in a moment after that day comes into view and out again after 5 seconds or at the first touch, and isn't shown when requests are off. After the arrival, its bubble says "Arriving … — now tap your departure day.". Amber days can be the arrival too ("Awaiting confirmation. You can still send a request."); a grey day says "Not available". The stay is marked as the guest moves over the calendar, with the dates and number of nights in the bubble (on a phone, in the bubble at the departure tap, just before the form opens), and days past the next fully booked night are faded — they can't be the departure; tapping one starts afresh with it as the arrival. To start over, tap the arrival again, the × in its bubble (Clear) or press Esc. A form opens with those dates as Arrival and Departure — they can be changed there too (again, not to fully booked nights). It asks for name, e-mail, phone (optional), the property's own questions and a message. If an answer doesn't seem to fit its question, the form says so ("Does this answer the question? Fix it or send anyway.") and the guest can fix it or Send anyway. After sending, the guest only sees "Request sent" — no e-mail.

The request appears in the booking list under Requests and an e-mail goes to the notification e-mails; replying to it writes to the guest. A request holds no dates: decide on the booking page (see bookings).

Which questions guests get: on Booking fields, tick Ask in the request form for a custom field (e.g. number of people, pets, car). The guest's answer is saved in that field. The question is shown in the guest's language; ones left blank are written automatically when you save, and you can change them. Answers are free text.