Events
LIGR sends one POST per change to every webhook that subscribes to the competition. Each event names one entity and one verb.
Event matrix
Section titled “Event matrix”Set subscriptions per webhook and per competition in the dashboard. Select the entities you want. A selected entity sends all of its events. LIGR drops the other entities before it queues a delivery.
| Entity | create | update | delete | Fires when |
|---|---|---|---|---|
match | ✓ | ✓ | — | A match is created, its details or lineups change, or a fact changes its score, clock, period or status |
fact | ✓ | ✓ | ✓ | A fact is created, edited, undone or deleted |
summary | ✓ | ✓ | ✓ | The match summary is recomputed or rebuilt. A rebuild sends a delete, then a create with a new id |
team | ✓ | ✓ | — | A team in the competition changes |
competition | — | ✓ | — | The competition itself changes |
overlay | ✓ | ✓ | ✓ | An overlay of a match is created, its settings or its key change, or it is deleted |
A fact is a goal, a card, a point, a substitution or any other time-stamped match event.
A new fact sends a match.update after the fact.create and the summary.update. When LIGR
adds several facts at once, for example from one provider update, it sends one match.update for
the batch. A fact that LIGR already has sends no fact.create and no match.update.
A match is never deleted. A match that leaves the schedule is cancelled, abandoned or finished
early. That arrives as a fact.create named MATCH_CANCELLED, MATCH_ABANDONED or
MATCH_FINISHED_EARLY, then a summary.update, then a match.update with finishedStatus set.
Read the status from match.update.
An overlay event fires for the overlay record: name, key, graphics delay, Auto Graphics, ad type,
theme setting and control room. A graphic shown or hidden on the overlay is not an overlay event.
An overlay that belongs to no match fires nothing, because there is no competition to route it to.
Order and volume
Section titled “Order and volume”match.*,fact.*,summary.*andoverlay.*for one match arrive in order, one delivery at a time, in the order the change happened. A retried delivery is the exception: it can arrive after a newer event. Comparedate.- Events across matches have no order guarantee.
- A live football match produces tens of events. A
summary.updatefollows most fact changes. Amatch.updatefollows each new fact or batch of new facts.
Subscribe only to the entities you handle. Every extra event costs your endpoint time, and a slow endpoint fails the 10-second timeout. See Delivery health & logs.