Spatial API Integration: How Partners Ship in Days, Not Months

Every integration starts with a question: what data do I get, and how do I get it? The Spatial API answers both with a stable contract and documented patterns.

The integration surface#

The Spatial API exposes venue data through three primary patterns:

Event subscriptions#

Real-time entity events (detections, state changes, zone transitions) delivered as typed messages. Partners subscribe to the events they need and ignore the rest.

Graph queries#

Point-in-time queries against the Venue Graph. "Which entities are in zone A right now?" or "What was the occupancy of zone B at 14:30?", answered from the versioned graph state.

Batch exports#

Historical data for analytics, model training, or compliance reporting. Exported with full provenance metadata and schema version tags.

Sandbox to production#

Partners start in a sandbox environment with synthetic venue data that mirrors production schemas. The integration path:

1. Sandbox: build and test against synthetic data
2. Staging: connect to a non-live venue with real hardware
3. Production: receive live venue data under the published SLA

Each stage uses the same API contract. Code that works in sandbox works in production.

What partners build#

The Spatial API isn't prescriptive about what partners build. Broadcast graphics, analytics dashboards, security alerting, occupancy optimization. The API provides structured spatial data, and partners apply their domain expertise.

The contract stays stable. The products built on top keep evolving.