Local court server API

Game data stays at the club: match summaries, ball measurements, moments and video live on the court server in the club network and are served from there, with no internet needed. The cloud is for what is shared between clubs and the player app: bookings, wallet, rating.

Where to get what

The court server sends only match results, aggregated stats and clips for the player app to the cloud (see Court server and cloud). Full recordings, moments from every camera and raw ball measurements stay at the club and are available only locally.

Address

http://<court server address>:8016

• The court server is reachable in the club network. The club receives its address at setup; the default port is 8016.
• A court is referenced by its name as configured on the court server, URL-encoded (for example Court%201). The list of names is in the court_names field of /status.
• Responses are UTF-8 JSON. Some responses are the same structures the court screen and the club video wall use, so they include display fields (captions, thumbnail links). Court names, captions and player names come in the language the club set them in.

Integration key

The club system (accounting, CRM, video storage) sends the key in the X-Integration-Key header. The key opens read-only access to the game data listed below. It cannot control the court: score, line-up, sessions, service restarts, camera settings, live video and audio stay behind the staff PIN.

curl "http://<court server address>:8016/status" \
  -H "X-Integration-Key: <integration key>"

• One key per system: your accounting system and your CRM get separate keys, and either can be revoked without touching the other. The key is created on the court server and shown once; this documentation uses the placeholder <integration key>.
• To get one, contact your platform administrator with the club name and the system that needs access. New and revoked keys take effect after the court server services restart, which is done when no game is in progress.
• A wrong key, a path outside the list and any request other than GET return 401 bad_pin.

Methods

Open without a key: GET /health (server alive, how many courts are playing), GET /live.json (which courts are on air) and GET /live/{court}/state.json (on-air flag and score). They contain nothing beyond what the scoreboard shows.

Field names in /measure/* responses are currently in Russian; an English field map is available on request. If the database flag in these responses is false, the measurement database is unavailable, and an empty answer does not mean there were no rallies.

After a match: summary and video

S="http://<court server address>:8016"
K="X-Integration-Key: <integration key>"
C="Court%201"

# 1. Latest match summary on the court
curl -H "$K" "$S/match/summary?court=$C"
# → {"court": "Court 1", "t0": 1790863200, "day": "2026-10-02", "time_from": "18:00", "time_to": "19:28",
#    "sets": [{"team1": 6, "team2": 4, "unfinished": false}, …], "winner": 1,
#    "players": [{"name": "Alex", "team": 1, "phone_tail": "0001", "distance_m": 2350.4,
#                 "top_speed_ms": 6.1, "sprints": 14, …}, …],
#    "highlights": [{"title": "…", "duration_s": 18, "ready": true, "url": "…"}],
#    "match_video": {"duration_s": 5280, "ready": true, "url": "…"}, …}

# 2. Player analysis for that match (t0 from the summary)
curl -H "$K" "$S/match/report?court=$C&t0=1790863200"

# 3. Today's video: full match recordings only
curl -H "$K" "$S/archive/list.json?court=$C&kind=match&days=1"
# → {"items": [{"id": "…", "kind": "match", "day": "2026-10-02", "time": "18:00", "duration_s": 5280,
#               "cams": [{"cam": "hik101", "root": "rec", "path": "…", "size": 1834221568,
#                         "ready": true, …}], …}], "summaries": […], "truncated": false}

# 4. Download a camera file (root and path from the list, path URL-encoded)
curl -H "$K" -o match.mp4 "$S/archive/file?root=<root>&path=<path>&download=1"

• Collect video while it is on disk: recordings are kept for the number of hours in retention_h of /rec/status (72 by default) and then deleted.
• A file with ready: false is still being written; fetch it later.
• The summary endpoint returns the latest match on the court. To miss nothing, poll /archive/list.json: its summaries field has every match summary for the selected days.

Errors

• 401 bad_pin: no key, a wrong key, or the method is not in the key's read list.
• 400 unknown_court: no such court on the server; 422: a required parameter is missing (usually court).
• 404: no summary (no_summary), session (no_session_on_court) or file (not_found).