Skip to main content

Cancellation and No-Shows

This release is all about guests not showing up, and handling the situation nicely in accounting and hotel operations.

Cancellations

Each rate plan defines the conditions under which they can be canceled, by linking to a cancellation policy. Create the policies by calling POST api.apaleo.com/settings/v1/cancellation-policies When creating reservations, the cancellation fee and date will be calculated and stored on the reservation. Check it out on GET api.apaleo.com/booking/v1/reservations/{id} in the cancellationFee field. Now, the cancellation fee amount is currently not configurable, but always the whole amount. To give hotels the flexibility to chose lower fees or even waive it completely, posting the fee is not automatically triggered by cancelling a reservation, but requires a separate call: PUT api.apaleo.com/booking/v1/reservation-actions/{id}/cancel POST api.apaleo.com/finance/v0-nswf/folio-actions/{folioId}/cancellation-fee Cancelling the reservation will remove all un-posted line items from the folio, and posting the cancellation fee will add a new one, and post it without VAT to a special cancellation-fee account. We restricted posting cancellation fees to reservations that do not have prepayments, as we wanted to bring a first version live today - that's also why it's still marked as NSFW, not safe for work.

No-Show Handling

It's bad enough when guests cancel reservations, but sometimes they don't even do that, and just don't show up. apaleo will now automatically detect all reservations that should have been checked in but weren't, and sets their status to no-show. We then remove all line items that are not accommodation from the folio, and post the charges just as if the guest would be there. This is triggered by the good old PUT api.apaleo.com/operations/v1/night-audit endpoint. In a first version, no-show is a terminal status and the reservations can neither be canceled nor checked in. We recommend that you double check that calling the night-audit is the last action you trigger on a business day.
Similar to cancellation fees, we do not yet allow to specify the no-show fee and default to 100% of the accommodation charges, for the whole stay. This can be corrected later on by moving posted charges to the house account, and thereby waving the whole fee, or parts of it: PUT api.apaleo.com/finance/v1/folio-actions/charges/{id}

We'll enhance the functionality around cancellations and no-show handling in future releases, but would be happy if you'd already try it out and give us feedback on api@apaleo.com. Stay tuned for updates!

❤ Your apaleo team

Comments

Popular posts from this blog

Getting Started with apaleo APIs

Have a look You can find all of apaleo's API on api.apaleo.io. We use Swagger to describe it, and to generate our documentation.

Sign up The first step is to sign up for an account. After you finish signup you will be able to login to our apaleo app and start configuring your properties. Also you can use the same credentials to access our API using Swagger. Get access for app We're still new and want to get in touch with you before we grant you access. Contact us at api@apaleo.com, to get your very own client credentials that lets you play with the API in our sandbox.
Use it apaleo APIs are protected using OAuth2 - the de-facto standard for API security. Here's a short guide to get you started:

Step 1: To get access to our APIs, you need to use your client id and secret to obtain an access token. Don't have one? Contact us at api@apaleo.com.

Combine your client id and secret into a string, separated by colon yourClientId:YourClientSecret and encode with Base64. This wi…

Connect your app with OAuth 2.0

What is this all about? When you connect your app to apaleo, it can read or modify data, or even trigger entire business flows of a hotel. But before gaining access to any of the resources in the REST API, it must get permission from the hotel. This guide will walk you through the authorization process (described in greater detail by the OAuth 2.0 specification). Note: apaleo's OAuth 2.0 implementation supports the standard authorization code grant type. You should implement the application flow described below to obtain an authorization code and then exchange it for a token. (The implicit grant type is not supported.) Terminology Before learning more about the details of the authorization process, make sure that you are familiar with some of the key terms that are used in this guide: Client: Any application that would like access to a hotel's data. A user (usually the hotel's owner or admin) must grant permission before the client can access any data.API: apaleo REST API. T…

Channel Integration Guide

With the channel integration you can subscribe for availability, rates and inventory (ARI), create new bookings and modify existing bookings. 
The BasicsGet your sandbox account and check out this guide to learn how you can connect to the apaleo APIs.
API Client All apaleo APIs are described as swagger documents. That lets you generate API clients directly from the swagger.json files. There is a large community, providing client generators for almost every language. For example, swagger code generator is a good project, which allows generation of API clients for Java, PHP, C#, NodeJS and more. This gets you up to speed very fast and as a bonus you can access API documentation within the auto-generated methods and models.
Sandboxapaleo.io is our – and your – playground to do first steps with the API, up to your final integration. Use it to interactively explore the API or to learn the apaleo concepts by navigating the user interface.

These are the links you need to know