Domain objects
This section describes the domain models used in TimeTime.in to describe reservation management problems.
Glossary
CALENDAR
A collection of related events with metadata such as name, description, default time zone, and owner. Calendars can be provided by third parties (Google, Microsoft) or by TimeTime itself. Each calendar contains multiple calendar events.
CALENDAR EVENT
An event associated with a specific date or time range within a calendar. Contains information such as summary, description, location, status, attendees, attachments, and comments. Calendar events are synchronized with external calendar providers.
ATTENDEE
A participant invited to a calendar event. Each attendee has a response status (NEEDS_ACTION, DECLINED, TENTATIVE, or ACCEPTED), contact information (email, phone, display name), and may have an associated invitation for RSVP management.
INVITATION
An object representing a request for a person to attend a calendar event. Contains event details (summary, subtitle, description) and display configuration for event times. Invitations allow guests to confirm or decline their attendance through dedicated endpoints.
BOOKING
A reservation made for an event type at a specific time. Bookings are associated with a booker, answered questions, resources, optional pricing information, and can be in different states (confirmed, on hold, cancelled). Each booking generates a corresponding calendar event.
EVENT TYPE
A template or service definition that can be booked. Defines characteristics such as duration, availability rules, required resources, pricing policy, workflows, and booking mode. Event types generate bookings when reserved.
RESOURCE
A bookable entity required for a reservation (e.g., a person, space, or equipment). Resources are organized into resource groups and can have their own availability rules. Event types specify which resources are needed for bookings.
AVAILABILITY RULES
Rules that define when a service or resource can be booked. Include repeating schedules, booking notice requirements (min/max), buffers before/after events, maximum concurrent bookings, and other time-based constraints.
WORKFLOW
An automation that triggers actions based on specific events. Workflows can be attached to event types and execute actions such as sending email or SMS notifications, reminders, or follow-up messages when triggers occur (e.g., booking confirmed, event starts, event ends).
PRICING POLICY
A set of rules that define how services are priced. Includes a default price specification (fixed or tiered), optional conditional overrides based on schedules, currency, and tax specifications. Pricing policies can be owned by users or organizations and are applied to event types.
TAX SPECIFICATION
A tax configuration within a price specification. Defines tax name, type (percentage or fixed amount), value, and whether the tax is included in the displayed price or added on top. Multiple tax specifications can be configured per price specification.