Timekit

If you just need to work with Timekit out-of-the-box, please refer to <a href="http://help.timekit.io/welcome-to-timekit/introduction/understand-timekit-with-this-glossary">our glossary</a> In Timekit terms, a booking is a request to occupy a time-slot in a calendar.

Each booking follows a set of steps, before it is complete, these steps are defined by workflows that we call graphs. We'll get more into details about the workflows later on in the article <a href="http://help.timekit.io/working-with-the-api/bookings/introduction-to-booking-graphs">Intro to booking graphs</a>, but for now lets just imagine a workflow that consists of these steps:

A customer requests an appointment with you, at a given time-slot.

You either confirm or decline the request.

You might have to cancel the appointment.

- A customer requests an appointment with you, at a given time-slot.
- You either confirm or decline the request.
- You might have to cancel the appointment.

These steps are what we call a confirm/decline workflow. It is important to know that your calendar will not be blocked at the requested time-slot, before the booking is confirmed. If you need your calendar to be blocked immediately when the request is send, you need to use a different workflow.

For a deeper look into our supported workflows, please refer to the <a href="http://help.timekit.io/working-with-the-api/bookings/introduction-to-booking-graphs">Introduction to booking graphs</a> Before you dive directly into our tutorial on <a href="http://help.timekit.io/working-with-the-api/bookings/creating-a-booking">how to create a booking</a>, please make sure you've first of all <a href="http://help.timekit.io/working-with-the-api/resources/creating-resources">created a resource</a>.

This article gives an introduction to the concept of bookings when working with the API.

Next steps