Hearing about changes with webhooks
A webhook is a message LEKKIN sends to your system when something changes. It says what changed and where to look; your system then fetches the details with its key.
Adding one
- On an integration’s card, press Webhooks, then Add a webhook.
- Enter the URL LEKKIN should send to. It must be
https. - Under Tell it when, tick the changes you want to hear about. You can only tick what the integration is allowed to read.
A signing secret is shown once. Copy it into your system: it’s how your system checks that a message really came from LEKKIN.
What you can hear about
- A fixture is added, changed (moved, rescheduled, a new venue) or removed.
- A result is recorded, changed, confirmed, contested or removed.
- A squad changes: somebody joins or leaves a team.
- A booking on one of your pitches is made, changed or cancelled.
What a message contains
Very little, on purpose. Each one says what kind of change it was, which thing it was about, and the API address to fetch it from. It carries no personal data. Your system fetches the details with its own key, so it only ever gets what that key is allowed to see.
Every message is signed in the lk-signature header with your signing secret. Check it before trusting the message.
If your system is down
LEKKIN tries again, several times, with longer gaps between tries. Each webhook shows how its recent sends went. Press Send a test to send one now while you’re setting up.
Changing or removing one
Change alters its URL or what it hears about. New secret replaces the signing secret, shown once again. Remove stops it.