Graphs & actions
Graphs are the "blueprints" that bookings are based on. They define different actions and transitions that bookings can go through, based on your business logic
Actions are transitions between steps in your graph, such as confirming, cancelling or rescheduling a booking. Some actions are triggered manually by you through the API, where others are autoplaying (internal steps) that happen automatically in a sequence. For instance, when you call the "confirm" action, the booking engine could automatically create a calendar event, send out an email notification and trigger a webhook before reaching the "confirmed" state.
As actions are different based on your specific graph, please refer to the reference below.
Available graphs
1-to-1 bookings
instant The instant graph represent the simplest flow possible where bookings are auto-confirmed upon creation. Cancellation is possible. See diagram.
instant_payment Build upon the instant graph by providing practical actions and states to be used in payment processing flows. Note that Timekit doesn't handle any payment processing natively; that's up to you to handle. See diagram.
confirm_decline If your bookable resources (e.g. vendors/suppliers) needs to either confirm or decline an incoming booking before it is accepted, you should use this graph, as it has an intermediary "tentative" state. See diagram.
Many-to-1 (group) bookings
group_owner This graph represent a bookable timeslot and acts as a "container" for all attached customer bookings. It also contains information on the number of seats (i.e. customer bookings) available. See diagram.
group_customer When a customer books a seat in your defined timeslot, you'll use this graph. You "connect" it with your container booking through the "owner_booking_id" property. See diagram.
group_customer_payment Comparable to the "group_customer" graph, but with a few actions and states that make it useful in scenarios where you want to receive payments before a booking is confirmed. See diagram.
Diagram explanation
Blue states are states where you can make an active choice.
Grey states are internal "autoplay" state that does a single job (send email, trigger webhook etc) and immediately trigger the next in line when done.
Black lines are transitions (actions) that you take, with the action name as the adjacent label