Pulse runs on the court, not in the cloud. Your edge box pushes events to a Pulse
host on the venue’s local network — a wired or strong-WiFi link.
How it works
1
Your edge box detects an event
A bounce, a hit, a speed reading — whatever the sensors see.
2
It POSTs the event to Pulse
One authenticated call to
POST /v1/events, over the local network.3
Pulse accepts and orders it
Pulse de-duplicates, orders by occurrence time, and feeds the live game rules.
The whole API, in one endpoint
The protocol is deliberately small: one endpoint, one envelope, a handful of event types. Everything else is semantics — how events are ordered, de-duplicated, and confirmed.Quickstart
Send your first event and get a
202 back.Endpoint reference
POST /v1/events — envelope, headers, batching.Event types
The five sensor events and their payloads.
Delivery semantics
Idempotency, ordering, preliminary → confirmed.