Different ways of using Timekit
There are basically 3 ways of working with Timekit, where you use one or more of the parts of our platform, depending on the complexity of your needs and/or special business considerations like custom emails, existing calendar UI etc.
100% out-of-the-box, no coding necessary. When you just need basic booking and our tool-set fully covers your needs.
Custom booking.js/widget configuration, when you need some special configuration of the widget, that you cannot do through our admin config tool, like month view instead of day-view or actions on callbacks.
Direct API integration. Where you handle all UI, or maybe just the customer-facing UI yourself, but need us to take care of the complexities regarding availability, calendar syncing and booking-flow.
Of course there are many more ways to use Timekit that are in-between these scenarios, but this gives you a good overview of the boundaries.
Concrete guides to how you start using Timekit
These guide will help you get up-and-running in each of the previous three scenarios.
It is a very good idea to familiarize yourself with the Timekit concepts, at least before you try out “Customized widget” and “Direct API integration”.
Out-of-the-box
Prerequisite: Sign up and make an app.
Just follow this guide.
Customized widget
Prerequisite: Sign up and make an app.
There are countless ways to customize the widget, which is also setting up the booking flow, defining availability-filters according to business rules e.g. business hours.
Here is an introduction to how you customize the widget.
TODO: small list with examples and a link to a list with widget tutorials.
You can also read the booking.js widget documentation for a complete reference.
Direct API integration
Prerequisite: Sign up.
Since almost all calls to the API are done in an application context you need to create an app as
the first thing.
Then you can basically follow this guide.
Updated about 7 years ago