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

Set subscriptions per webhook and per competition in the dashboard. Select the events you want. LIGR filters everything else before it leaves the queue.

Entity	create	update	delete	Fires when
match	✓	✓	—	A match is created, or its details, status, score, clock or lineups change
fact	✓	✓	✓	A fact is created, edited, undone or deleted
summary	—	✓	✓	The match summary is recomputed. A delete carries ids only
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 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.

Caution

summary.create and competition.create do not exist. A summary starts to exist with its first update. A competition is created in the dashboard, not through an event. match.delete, team.delete and competition.delete do not exist.

Order and volume

• match.*, fact.* and summary.* 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. Compare date.
• Events across matches have no order guarantee.
• A live football match produces tens of events. A summary.update follows most fact changes.

Subscribe only to the events you handle. Every extra event costs your endpoint time, and a slow endpoint fails the 10-second timeout. See Delivery health & logs.