Getting started
Open the Events Portal, add a destination, and confirm your first delivery.
Events
Levno Events pushes farm events to you as they are detected, so you do not have to poll for them. You register one or more destinations — normally an HTTPS endpoint on your side — and Levno sends a small JSON payload to each one every time a subscribed event happens on a farm your organisation has access to.
It is designed to be used alongside the Levno for Partners application and REST API. A REST API key does not verify an incoming webhook — see verifying webhooks for the separate credential used for that.
Understand the payload
Learn how the event envelope, subject, and delivery fields fit together.
How it works
Section titled “How it works”- Something happens on a farm — a milking finishes, or a tanker completes a collection.
- Levno builds a payload describing what happened.
- The payload is delivered to every destination you have configured for that event’s topic.
- Failed deliveries are retried automatically. You can inspect and replay them in the portal.
Terms used in these docs
Section titled “Terms used in these docs”| Term | Meaning |
|---|---|
| Event | One thing that happened, on one farm, at one point in time. |
| Topic | The event’s name — what you subscribe to, e.g. levno.milking.finished. |
| Destination | Where Levno sends events — an HTTPS endpoint you own. |
| Delivery | One attempt to send one payload to one destination. Retried on failure. |
| Portal | The self-serve web page where you manage destinations and inspect deliveries. |
Available events
Section titled “Available events”Three events are available. The first reports the farm’s total milk volume across every vat whenever a milking or collection finishes; the other two report that single vat’s own finished operation.
levno.farm.milk.volume.updated— a milking or collection has finished and the farm’s total milk volume, summed across all its vats, has changed as a result.levno.milking.finished— a milking on the farm has finished and its volume has been measured.levno.collection.finished— a tanker collection from the farm has finished.
You receive events only for the farms your organisation has access to in the Levno for Partners app. If a farm is added later, events from before that point are not sent.
Learn more
Section titled “Learn more”- Getting started — request access and add your first destination.
- The portal — manage destinations and review delivery history.
- Destinations — what a webhook endpoint needs, and alternatives to HTTPS.
- Event model — the payload shape for each event type.
- Receiving events — prepare an endpoint to accept deliveries.
- Verifying webhooks — confirm a payload actually came from Levno.
- Delivery and retries — timeouts, retry schedule, and deduplication.
Support and feedback
Section titled “Support and feedback”For help accessing the Events Portal, or with an integration, contact your Levno account manager.
When reporting a delivery problem, include the payload’s id, its delivery.id, and roughly when it happened. That is enough for Levno to find the delivery and the response received.