The Booking object represents a scheduled time allocation for a person, serving as a core component for tracking time, managing availability, and organizing resource allocation. There are two main types of bookings:
Budget bookings - where a person is allocated to work on a specific deal/budget. These bookings are linked to a service object, which represents the actual work being done.
Absence bookings - which track time off and remote work absences. These bookings are linked to an event object, representing the type of absence (time off or remote work).
Each booking method defines how time is allocated and requires specific attributes to be set: Per day (requires hours and time attributes to specify hours and time for each day), Percentage (requires percentage attribute to allocate a portion of a person's available time) and Total hours (requires total_time attribute to specify the total amount of hours for the selected period).
Bookings can have different states depending on their type:
draft: true) or ConfirmedBookings can also be customized with custom fields to store additional information about booking. Custom fields allow you to add custom attributes or any other metadata relevant to your booking workflow. For more details on how to work with custom fields please refer to Working with custom fields guide.
The following diagram shows bookings in our data hierarchy:
Internal field used for date-range filtering.
Whether the booking has been approved. Reflects the overall approval_status.
1
2
3
5
Per-approver approval status records for this booking.
Indicates whether the booking has been approved.
Timestamp when the booking was approved, or null if not yet approved.
The person who approved this booking.
The ID of the person who approved this booking.
Array of IDs of files attached to this booking.
Files attached to this booking.
When true, time entries are automatically tracked against this booking.
Internal field used for date-range filtering.
ID of the billing type of the associated service.
1
2
3
4
ID of the booking method used to create this booking (e.g. hours per day, percentage, total hours).
1
2
3
Whether this is a project booking or an absence booking.
ID of the budget (deal) associated with the booking's service.
Whether this booking has been canceled.
Date when the booking was canceled.
The person who canceled this booking.
ID of the client company associated with this booking.
Date when the booking was created.
The person who created this booking.
File attachments linked via custom fields on this booking.
People linked via custom fields on this booking.
Custom field values for this booking.
Whether the booking is tentative (draft) or confirmed.
Booking end date.
The absence event category (e.g. vacation, sick leave) for absence bookings.
ID of the absence event category for this booking.
External identifier for integration with third-party systems.
Scheduled hours per day for this booking.
Unique identifier of the booking.
Timestamp of the last activity recorded on this booking.
An optional note or description for this booking.
The organization this booking belongs to.
The booking origin (e.g. the resource request that generated this booking).
The ID of the origin record (e.g. resource request) that created this booking.
Custom field values defined on the assigned person.
Scheduled time as a percentage of the person's daily capacity.
The person assigned to this booking.
ID of the person assigned to this booking.
ID of the subsidiary the assigned person belongs to.
Type of the assigned person (e.g. employee, contractor, placeholder).
1
2
3
4
ID of the project this booking relates to.
Type of the associated project (e.g. billable or internal).
1
2
Whether this booking has been rejected.
Date when the booking was rejected.
Reason provided when the booking was rejected.
The person who rejected this booking.
The resource request this booking fulfills, if applicable.
ID of the resource request this booking fulfills.
The scenario item this booking is linked to, if created from a scenario.
The budget service being scheduled in this booking.
The ID of the service this booking is scheduled against.
The stage type of the booking within the resource planning workflow.
1
2
The start date of the booking.
The current approval status of the booking (e.g. pending, approved, rejected).
Tags associated with this booking.
The task associated with this booking, if applicable.
The ID of the task associated with this booking, if applicable.
The booked time in minutes per day.
The total booked time in minutes across the entire booking period.
The total number of working days covered by this booking.
Timestamp when this booking was last updated.
The person who last updated this booking.
When true, cost calculations use the person's salary currency instead of the service currency.
When true, draft bookings are included in availability and planning views.