Partner API

LedsCount Partner API.

Two-way data exchange between your tournament software and our hardware. REST or WebSocket — same API key, same functionality, pick what fits your stack.

Base URL: https://webservices.ledscount.com

Mode

REST API

HTTPS request/response. Simple integrations, polling, server-to-server.

REST reference →

Use one or both — REST is the simplest start, WebSocket adds real-time push events as they happen.

Authentication

Each partner receives an API key. The same key is used for both REST and WebSocket connections. 

REST:       X-API-Key header on every request
WebSocket:  ?apiKey=YOUR_KEY query parameter on connect
Optional:   IP whitelisting (REST only)
Rate limit: 60 req/min (REST only)
http

Quick start

  1. 1

    Get your API key

    One-time onboarding — how to start .

  2. 2

    Try the simplest call

    GET /api/partner/getMatchFormats confirms auth and lists supported scoring formats.

  3. 3

    Wire up startMatch

    Configure a scoreboard with player names — you're integrated.

Integration flow

A typical tournament match runs through five touchpoints. Most partners wire up steps 1, 2, and 4 first; streaming (step 3) and pager (step 5) come once the basics are in.

Match lifecycle
1. Tournament organizer creates tournament in your platform
2. When a match is ready to start:
   → Call startMatch (REST or WS)
   → The physical scoreboard resets and shows player names
   → Players score the match on the scoreboard
3. (Optional) Start a YouTube broadcast for the court:
   → Call startYoutubeStream with freshMatch:true
   → The encoder pushes RTMP to YouTube with the live score baked in as an overlay
   → Subscribe to partnerStreamStatus on the WebSocket for live state
4. During the match:
   → Live scores pushed automatically via WebSocket (scoreResponse messages)
   → Or poll GET /api/partner/getScore (REST)
5. When the match ends (playing = false):
   → Record the final score, advance the bracket
   → Call stopYoutubeStream to end the broadcast (or rely on the auto-stop timer)
text

A proper sequence diagram lands here in a later pass.

Onboarding

One-time per partner.

API key issued per partner. Customer ID mapping done at onboarding (your internal club ID → our LedsCount club ID). Court numbers must align across both systems — Court 1 = Court 1.

Onboarding flow →

Need a scoreboard to test with?

We lend integration partners a scoreboard during development.

Reach out and we'll ship one. Standard for every integration we've ever done.

Get the API key