Are you offering activities, guided tours, holiday rentals or any other bookable product online? To handle bookings, payments and customer confirmations, you will inevitably need to rely on technology — unless you plan to sit in front of your screen with your phone and card reader around the clock!
There are really only two ways to handle online bookings: you can either use a Widget or turn to an API. These are two concepts that aren't necessarily easy to grasp if you're unfamiliar with the complex world of online reservations. But don't worry — we'll explain everything!
What is the difference between a Widget and an API?
An API, on the other hand, is invisible to your site's visitors. It is used solely to exchange information between your website and the booking system. The booking itself must then take place within a booking module that you build yourself.
An example? Imagine your website is a restaurant and your visitors are customers walking through the door. The Widget would be the menu, while the API would be the order placed by your customers and sent directly to your kitchen.
One thing to bear in mind: a Widget must always be connected to an API in order to work, because the website calls the API, which checks the database to see whether the booking is available and, if so, confirms the purchase. All of this happens in a matter of milliseconds, of course! Conversely, an API cannot function on its own: it needs a shell to present it on your site, but that shell doesn't have to be a Widget.
Widgets don't exist solely for booking systems. You can, for example, use Widgets to display today's weather, a calendar, posts from your social media accounts or customer reviews of your products. They come in all shapes and sizes!
