Skip to content
CourtCatch

How CourtCatch works

Most clubs open their courts a fixed number of days in advance, at a fixed time. The popular slots are taken within seconds of that moment. CourtCatch does the same thing you would do by hand — log in, pick the court, add your partners, submit — except it does it at exactly the right moment, every time.

1. Link your KNLTB account

You search for your club and sign in with the same details you use for Mijn KNLTB: your federation membership number and your password. CourtCatch validates them straight away against the KNLTB API, so you know immediately whether the link works.

Your password and the session token are stored encrypted. They are used to sync your club data and to send the reservations you asked for — nothing else.

2. Sync your courts and buddies

Once the account is linked, CourtCatch pulls your club's courts and your KNLTB buddy list into the dashboard. Courts keep their club identity, including number, surface and whether they have lighting, so you can pick the exact one you want rather than "any court".

You can re-run the sync whenever your club adds a court or you add a new playing partner.

3. Build a booking schedule

A schedule is the description of the slot you want. You set it up once and it keeps working.

  • The court you want, plus an optional fallback court.
  • The buddies who should be on the reservation. You are always included.
  • The start time of the court itself — the hour you actually want to play.
  • How many days ahead your club opens the slot. Seven is common; your club rules decide.
  • The clock time reservations open at your club. That is the moment CourtCatch fires.
  • Whether this repeats: once, daily, weekly, or on specific weekdays, between a start and an end date.

4. The moment itself

Shortly before the opening time, the job for your schedule is already awake. Two seconds ahead it opens and warms a connection to the KNLTB API, so the handshake is out of the way before it matters. The remaining milliseconds are waited out precisely, and the reservation is sent at the target moment rather than a fraction of a second after it.

Everything that can be prepared in advance — the request body, the log entry, the connection — is prepared in advance. What is left at the opening second is the request itself.

5. When something is in the way

Two things typically go wrong at the opening second, and CourtCatch reacts to both without you being there.

  • The court is already gone. If you configured a fallback court, the reservation is immediately retried on that court.
  • A playing partner is already booked. KNLTB refuses a reservation when someone on it is playing elsewhere at that time. CourtCatch swaps the blocking partner out and tries again — either for any available buddy, or for one from a shortlist you chose in advance.

6. What you get back

After every attempt you get a notification in your dashboard telling you which court was booked, or why it did not work out.

Every attempt is also written to an attempt log: the request that was sent, the response from KNLTB, the response code and the final outcome — booked, failed, court conflict or buddy conflict. If something goes wrong, the evidence is there instead of lost.

What you need

An active Mijn KNLTB account at a club that uses online court reservations, and a club that opens its courts a fixed number of days in advance. If your club releases courts on an irregular schedule, there is no fixed moment to aim for and CourtCatch cannot help you.

You keep using your own KNLTB account, and you can keep booking by hand exactly as before.

Ready to set up your first schedule?

The Free plan lets you run a real booking before you pay anything.