Docs Portal
Connector Guides
API ReferenceConsole

OfficeSpace Source

Office Space logo

The OfficeSpace Source connector integrates with OfficeSpace Software's workspace management platform to bring building, floor, space, and workspace data into the Mapped graph. This connector synchronizes organizational workspace information including rooms, desks, and neighborhoods, enabling comprehensive space utilization and workplace analytics.

Use Cases

  • Space Management: Visualize and analyze workspace allocation across buildings, floors, and neighborhoods to optimize space utilization
  • Desk Booking Integration: Connect workspace data with occupancy systems to enable intelligent desk and room booking workflows
  • Workplace Analytics: Track workspace distribution and availability patterns to support real estate and facilities planning decisions

Configuration

Auth Requirements

To connect to OfficeSpace, you need an API Key: A valid OfficeSpace API key with read access to sites, floors, rooms, and seat information

The connector will validate your credentials during setup by attempting to retrieve site data from the OfficeSpace API.

Place Mappings

The connector maps OfficeSpace organizational structure to Mapped's place hierarchy. Configure the following mappings:

FieldRequiredDescription
building.siteIdYesThe OfficeSpace site ID to map to a Mapped building
building.nameYesThe name of the building/site
building.addressYesThe full address of the building
floor.nameYesThe floor label (auto-populated from OfficeSpace)
floor.levelYesThe floor level/number
space.nameYesThe room name (auto-populated from OfficeSpace)
space.refIdYesUnique identifier for the room (must be unique)
space.codeNoAdditional room code or identifier

The connector automatically discovers all sites, floors, and rooms from your OfficeSpace instance and presents them for mapping configuration.

Mapped Concepts

API to Mapped Entities

OfficeSpace ObjectMapped Entity TypeDescriptionRelationships
SiteBuildingRepresents an OfficeSpace site as a buildingContains floors via hasPart
FloorFloorRepresents a floor within a sitePart of building via addPartOf, contains spaces via hasPart
RoomSpaceRepresents a room or area on a floorPart of floor via addPartOf, contains workspaces via hasPart
SeatWorkspaceRepresents an individual desk or workspacePart of space via relationship to parent space
NeighborhoodZoneRepresents a grouping of workspacesPart of floor via addPartOf, contains spaces and workspaces via hasPart

External Identities:

All entities are linked to their OfficeSpace source records via EXTERNAL_IDENTITY entities with URN format:

  • Buildings: urn:officespace:building:id:{site_id}
  • Floors: urn:officespace:floor:id:{floor_id}
  • Spaces: urn:officespace:room:id:{room_id}
  • Zones: urn:officespace:neighborhood:id:{neighborhood_id}

Workspace Hierarchy:

When rooms contain seats, the connector creates:

  • A Space entity for the room
  • Workspace entities for each individual seat
  • Optional Zone entities for neighborhoods (if seats are grouped)

Zones create additional relationships connecting workspaces to organizational groupings across the floor.

Sample Code

Query Buildings and their Floors

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
{
  buildings(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) {
    id
    name
    exactType
    identities {
      ... on ExternalIdentity {
        __typename
        value
        scope
        scopeId
      }
    }
    floors {
      id
      name
      exactType
      level
      identities {
        ... on ExternalIdentity {
          __typename
          value
          scope
          scopeId
        }
      }
    }
  }
}

Query Spaces, Workspaces and Zones on a Floor

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
{
  floors(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) {
    id
    name
    hasPart {
      id
      name
      exactType
      mappingKey
    }
  }
}

Query Zones (Neighborhoods) and their Spaces

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
{
  zones(filter: {connectedDataSourceId: {eq: "your-connector-Id"}}) {
    id
    name
    exactType
    mappingKey
    hasPart {
      id
      name
      exactType
      mappingKey
    }
  }
}

Query Workspace with parent Space and Zone

Request Response
Copy
1
2
3
4
5
6
7
8
9
10
11
12
{
  zones(filter: {exactType: {eq: "Workspace"}}) {
    id
    name
    exactType
    isPartOf {
      id
      name
      exactType
    }
  }
}

Graph Diagrams

Diagram of Building hasPart Floor, which hasPart Zone (Neighborhood) and hasPart Space. The Zone (Neighborhood) hasPart Space and hasPart Workspace, and in turn Space hasPart Workspace.