API Access and Tokens

Connect your own tools to your league: a club website showing live courts, a check-in kiosk, a results feed or a script that sets up tournaments. League admins turn on API access and create API tokens; developers use them with the official SDKs.

What an API token can do

A token belongs to one league and acts in it with the permissions you chose: reading players, courts and games, checking players in, starting and finishing games, running tournaments and seasons, exporting data or managing court bookings. It can never manage members, billing or API access itself, and it only reaches the public API, not the rest of the app.

Turn on API access

Go to Setup > API access and switch on Allow API access. API access is included in paid plans. Only admins with the Manage API Access permission see this page; an account admin can give it in Setup > Members. Turning the switch off refuses every token of the league without deleting them. Cached tokens on other servers may keep working until the cache expires (up to 60 seconds by default).

Create a token

Select Create token, give it a name that says what uses it, choose how long it lasts (up to one year) and tick the permissions it needs. You can only give permissions you hold yourself. The token is then shown once: copy it and store it safely.

The token is shown only once and works like a password for your league. Keep it on a server or in a secrets manager; never put it in a web page, a mobile app or a shared document.

Choose the smallest set of permissions

Give a token only what its integration needs. A scoreboard only needs View Courts; a check-in kiosk also needs Change Player Status. Actions done with a token are recorded under its name (API: name), so you can tell them apart from people in the league history.

Expiry and revocation

Each token stops working on its expiry date. Revoke a token from the list at any time: it stops working within a minute. Tokens belong to the league, so they keep working if the admin who created them leaves; any admin with the permission can revoke them. The list shows when each token was last used.

Webhooks

With API access on, you can add up to 2 webhooks in Setup > API access: League Dispatcher then posts every league event (check-ins, games started and finished, scores, tournaments, settings changes) to your server as it happens, with the same data the apps receive live. Webhooks only deliver while API access is on and your plan includes it.

When you add a webhook, League Dispatcher first sends it a verification challenge, which your server must send back; until it does, the webhook stays "Not verified" and gets no event, so nobody can point webhooks at a server that did not ask for them. Use Verify once your server is ready, and again after changing the URL. Choose how your server recognizes League Dispatcher. Signature (recommended): every delivery is signed with a secret generated for you and shown once, following the Standard Webhooks format, so a forged or replayed request is rejected; rotate it at any time, the old secret keeps signing for 24 hours. Shared secret: your own secret is sent as is in a header you name (for example Authorization). Either way you can rename the header, and each delivery also carries the league's id and name.

Use Send a test event to check your endpoint. A failed delivery is retried a few times with the same webhook-id, so your server can ignore duplicates. After 5 failures in a row, deliveries stop for a minute and then one retry decides: the wait doubles after each failed retry, up to an hour, and events are not resent meanwhile. A successful test resumes deliveries at once. An endpoint that keeps failing for about two days is paused and shows the last error; fix it, then turn it back on in its settings.

For developers

Official SDKs for TypeScript, Python and .NET, with ready-to-run samples. They are experimental: a new release may require changes to your integration. See the developer guide.

Every operation the API tokens can call, with its parameters, responses and examples, is listed in the API reference.