Docs Portal
Documentation
API ReferenceConsole

Calendar Events

Calendars and CalendarEvents model scheduled activity in your Mapped graph. Use them to represent room bookings, meetings, and reservation lifecycles, then connect those events to physical places (like Spaces and Buildings) for analytics and downstream workflows.

Use Cases

  • Space utilization analytics: Measure booking demand, identify underused rooms, and compare utilization across floors/buildings.
  • Event-driven building operations: Trigger or optimize HVAC, lighting, AV, and cleaning workflows based on upcoming room reservations.
  • Workplace experience applications: Power room availability views, workplace wayfinding, and schedule-aware employee experiences.
  • Portfolio-level planning: Aggregate event trends across buildings to support real estate and operations decisions.
  • Downstream system synchronization: Send normalized booking events to external systems while preserving identity linkage to avoid duplicates and support updates.

Calendars

A Calendar serves as the container for scheduled items related to a place or resource. It represents a scheduling context (for example, “Room A booking calendar”), connects to a place or resource entity in the Graph, and typically contains many CalendarEvents over time.

You can query Calendars and their related Spaces:

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
{
  calendars {
    id
    name
    exactType
    isCalendarOf {
      __typename
      ... on Space {
        id
        name
        exactType
      }
    }
  }
}

Likewise you can query Calendars by Spaces:

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
{
  spaces {
    id
    name
    exactType
    mappingKey
    hasCalendar {
      id
      name
      exactType
      hasCalendarEvent(filter: {startTime: {gte: "2026-06-01"}}) {
        id
        name
        exactType
        startTime
        endTime
      }
    }
  }
}

CalendarEvents

A CalendarEvent is a single booking or scheduled event instance with a start time and end time. It's linked to the Calendar it belongs to and the Space or location where it occurs.

You can query CalendarEvents and their related Spaces:

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
{
  calendarEvents {
    id
    name
    startTime
    endTime
    hasLocation {
      ... on Space {
        id
        name
        exactType
      }
    }
  }
}