Concepts
A minimal vocabulary you need before writing any code.
| Term | Meaning |
|---|---|
| Organization | A ZenSpace tenant (one customer company). You integrate against one organization at a time. |
| Space group | A logical grouping of meeting spaces (e.g. a building or floor). Carries timezone and address. |
| Meeting space | A reservable room. Each space has an operating_mode: zenspace, hybrid, or third_party. Your bridge integrates with spaces in third_party mode. |
| Operating mode third_party | The external calendar (your system) owns the booking lifecycle. ZenSpace mirrors it for reporting, access credentials, and device integrations. |
| Connection | A registered integration between your system and one meeting space, for one mode. Has a lifecycle: pending → approved → suspended. |
| API key | The credential your bridge uses. Issued by an organization admin, scoped to the organization. Sent as x-api-key header. |
| Booking | A reservation on a meeting space for a time window. This is what your bridge pushes into ZenSpace on every calendar event. |
| Physical-space mapping | Optional link from a ZenSpace meeting space to a physical door/lock/wifi device. When present, ZenSpace can auto-generate access credentials at T-15 before a booking starts. |
Rule of thumb: A third_party space is invisible to ZenSpace’s public booking app. All bookings must be pushed through the API by your bridge.