Connecting your club’s website or systems
LEKKIN has an API, so your club’s website, membership system or booking form can work with your fixtures, results, squads and facility bookings. Here’s how it fits together before you build anything.
What you can connect
Anything your club runs that could use its LEKKIN data. The common ones:
- Your website, showing this weekend’s fixtures and last week’s results.
- A membership system, adding players to squads so nobody types them in twice.
- A booking form, checking when a pitch is free and booking it.
Each thing you connect is an integration. It belongs to the club, not to whoever set it up, so it keeps working when people move on.
Who can use it
Open Developers from the menu at the left of the top bar in any LEKKIN app: press your club’s badge, and your apps are listed under your clubs. It’s there for club admins, and for anybody the club has given the Developer role, which a club admin grants from People → Staff & access in the Club Hub. That role is for the person who builds your website: it can manage the club’s integrations and nothing else.
Where it opens
Developers opens on its Dashboard: anything that needs you (a webhook that was switched off after failing, a key about to run out, a key nothing has used for a month), how many integrations, keys and webhooks the club has, and each integration with when its keys were last used. Connect in the menu is where you add and change integrations.
The sandbox and live
You start on Live, your real club. To build safely, choose Sandbox in the menu: it switches you over and opens the Sandbox page. Inside, the same menu item reads Exit Sandbox and brings you back.
- Sandbox is a copy of your club with your name and colours, filled with test data: teams, squads, fixtures, results and bookings. Keys made here are test keys. Nothing you do there touches your real club, and emails it would send are caught and shown to you instead. Every club can use it, free. See Building in the sandbox.
- Live is your real club. Live keys need the developer platform add-on, which can be tried free for 30 days. See Going live.
A club that hasn’t added it yet sees that on Live, with a way into the sandbox, so you can start building straight away.
What an integration can see
On purpose, very little about people. A player is a name and a squad number: no date of birth, no guardian’s contact details, nothing medical. Bookings show when and where, not who booked or what they paid. And each integration can only do what you ticked for it. The privacy notice sets this out in full.
The reference
API docs in the menu lists every call, what it needs and what it returns. In the sandbox, paste a test key at the top of the page and press Try it on any call to send it from the page.