Skip to content
Surfing Dog Surfing Dog Inbox

apaleo

Not switched on yet. This connection is built and switched off. A hotel connects an app on apaleo’s own page, and the app is registered with apaleo by whoever runs the Inbox server; the hosted inboxes at surfingdog.ai don’t have one yet. A hosted inbox shows apaleo as Soon; on your own server it says Needs setup until its connect client is set. Until then, stays come to you as requests and you confirm each one.

What it needs

Section titled “What it needs”
  • An apaleo connect client, registered with apaleo, with an https address to come back to. Whoever runs the Inbox server holds its id and secret.
  • Then, for you: Continue with apaleo, approve on apaleo’s page, and choose which of your properties this Inbox is.

A second way, where a hotel makes its own simple client in apaleo (Apps → Connected apps), is built too and stays off: apaleo recommends that way only for a hotel’s own internal apps.

What apaleo is asked to allow

Section titled “What apaleo is asked to allow”

Read your rooms (unit groups), rate plans, rates and availability; read offers; read and manage reservations. Never a permission to force a booking past what is free, never payment accounts and never card authorizations.

What it will do

Section titled “What it will do”
Reads Your properties, their time zones and currencies. Unit groups of bedrooms and how many units each has. Rate plans sold direct whose guarantee is a 6 pm hold. What is free night by night and each night’s price; a stay’s own total from apaleo’s offer.
Writes Each stay, before it is confirmed, as a direct booking with a 6 pm hold, its reservations carrying our reference and a comment with what the guest agreed. Changes and cancellations through apaleo’s own actions. The guest as the primary guest, once the stay is confirmed.
Never A price: apaleo prices each stay from its rate plan. A card, a payment account, an authorization or a commission.

Rate plans whose least guarantee in apaleo is a card or a prepayment are left out: your Inbox never holds a card.

After each write your Inbox reads back what apaleo says the stay comes to. When that differs from what the guest agreed, you get a note on the stay, so the desk checks the folio before charging anything more.

How it keeps a room from being sold twice

Section titled “How it keeps a room from being sold twice”
  • Written first, once. Each booking is sent with a key of its own; apaleo answers the same request with the same booking for 24 hours, so a request sent again never books twice. After that, the booking is found by its reference.
  • Refused when full. apaleo refuses a night it cannot sell. The booking is never forced.
  • Changed room by room. For a stay of several rooms, if apaleo refuses the second, the first is put back, so the stay keeps its dates. If apaleo will not take the first back, you get a note that apaleo and your Inbox now hold the stay differently, to set right in apaleo. Rooms are matched by their own number, so the tenth comes after the second.
  • Your own date. Every time apaleo gives is read in your property’s time zone: a lodge east of the date line keeps its own dates.

apaleo has no holding state for a reservation, so a stay held for a few minutes, or waiting for its deposit, is a reservation your Inbox cancels if it is not paid in time.

Webhooks

Section titled “Webhooks”

Once the connection is kept (its first sync, a moment after you approve it), your Inbox subscribes to reservation events at its own address. apaleo sends that address a health check as it makes the subscription, and your Inbox answers it, so the subscription is switched on. A hosted inbox subscribes once it is live at your own address. apaleo does not sign its deliveries: the address is the secret, the account must be yours, and each reservation named is read back from apaleo before anything changes.

Documentation

Section titled “Documentation”