> ## Documentation Index
> Fetch the complete documentation index at: https://docs.playpicklx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PicklX Court Event Protocol

> How event sources feed real-time court data into PicklX Pulse.

PicklX Pulse is the orchestration engine behind a PicklX court — it ingests live sensor
events, runs them through deterministic game rules, and drives the on-court experience in
real time.

This is the **Court Event Protocol**: the single interface an event source (such as your
court's edge box) uses to send court events to Pulse.

<Note>
  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.
</Note>

## How it works

<Steps>
  <Step title="Your edge box detects an event">
    A bounce, a hit, a speed reading — whatever the sensors see.
  </Step>

  <Step title="It POSTs the event to Pulse">
    One authenticated call to `POST /v1/events`, over the local network.
  </Step>

  <Step title="Pulse accepts and orders it">
    Pulse de-duplicates, orders by occurrence time, and feeds the live game rules.
  </Step>
</Steps>

## 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.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="play" href="/quickstart">
    Send your first event and get a `202` back.
  </Card>

  <Card title="Endpoint reference" icon="code" href="/endpoint">
    `POST /v1/events` — envelope, headers, batching.
  </Card>

  <Card title="Event types" icon="list" href="/event-types">
    The five sensor events and their payloads.
  </Card>

  <Card title="Delivery semantics" icon="arrows-rotate" href="/delivery-semantics">
    Idempotency, ordering, preliminary → confirmed.
  </Card>
</CardGroup>