Hapio Logo

Features

What Hapio can do.

Hapio – the flexible booking system that is adapted to your needs

Our powerful basic system handles the most common needs of different booking processes – but you decide how to use the functions for your customers and their administrators. You as a developer can always check our API documentation for full insight, and some of Hapio’s features are described below.

Locations

With the help of Hapio, handling of bookings that are conducted in multiple locations is simplified.

Different types of services

To be flexible and useful for different types of businesses, Hapio supports different types of services. Fixed time is used for services that have a predetermined duration, where the customer only selects one of the available times. Flexible time is used for services where the customer chooses the length of the booking, based on the limits and criteria that have been set for the service in Hapio. 24-hour booking is used for services booked per day, where the start and end time for the service is started, and the customer only chooses the start and end date for the booking, based on the limits set for the service in Hapio.

Buffer time

Each service can have a buffer time both before and after a booking so that Hapio automatically sets aside time for preparation, cleaning and similar between bookings.

Booking window

Each service in Hapio may have a limited booking window, i.e. the time when it´s possible for the customer to create new bookings. It´s possible to specify partly how early the booking may take place, and partly how late the booking may take place. It is also possible to specify how close to a booking cancellation may take place.

Bookable times

For services that are booked according to a fixed or flexible time, it is possible to specify how closely bookable times are to be offered. It can be about e.g. a bookable time every 15 minutes, or once every hour.

Flexible schedules

Each bookable resource in Hapio has its own schedule that indicates when the resource is available for booking at a specific location. Hapio supports recurring schedules, which look the same week by week, but also suit businesses with regular opening hours. Hapio also supports schedule times that apply to specific dates, which is suitable for businesses with irregular opening hours. Recurring schedules can also be combined with date-specific schedule times so that it´s possible to open times outside the regular recurring schedule (e.g. during extra hours on a public holiday), and also block times within the regular recurring schedule (e.g. during holidays).

Automatic resource allocation

When a booking is created without a resource being specified, Hapio automatically assigns a resource to the booking based on a specific strategy. A strategy is selected for each location in Hapio, which makes it possible to use different strategies for different locations as needed. There are three strategies available.

Random selection

Hapio randomly selects one of the available resources.

Prioritization

Hapio is based on a priority order list for the resources and selects the available resource that has the highest priority.

Equalization

Hapio checks how much time is booked for each available resource, and selects the resource that has the least booked amount of time. This way, the load is spread evenly over the available resources.

Webhooks

With the help of webhooks, external systems can receive notifications at events in Hapio, and act on these. In this way, Hapio’s functionality can be expanded as needed, and it opens up further possibilities for integrating Hapio with other systems.

Permissions / Abilities

Each API token has its own permissions/abilities, which govern what is allowed to be done with each API token, such as trestricting certain API tokens to only create bookings according to the resource schedules, while other API tokens should be allowed to create off-schedule bookings.

If you have questions or wish to see other functions, do not hesitate to contact us, and do not forget to check our documentation.