Live event changes are expressed through the action field.
The possible values are ADD, UPDATE, and DELETE.
This page explains how UPDATE and DELETE messages are shaped.
Updates use the UPDATE action.
Updates follow a full payload pattern.
That means the message includes the changed fields and the unchanged fields in the same payload.
Consumers should replace the previously stored version of the event with the new one.
Deletes use the DELETE action.
The message identifies an event that was previously sent and should now be removed.
For DELETE, only id, action, created_at, and sport_event are included inside data.
The payload field is omitted.
data.id refers to the previously sent event that is being deleted.
Treat UPDATE as a replacement of the previous event version.
Treat DELETE as removal of the referenced event.
Use data.id as the stable event identifier across versions.
The outer WebSocket envelope stays the same. Only the data.action and data content differ.
Last updated
Was this helpful?
Was this helpful?
{
"specversion": "1.0",
"id": "0da2b5ba-b92f-42bd-b9d2-0fcd978fec85",
"source": "/tournaments/1971",
"type": "Event.Sport.Golf",
"time": "2026-05-04T14:23:01.123Z",
"tournamentid": 1971,
"datacontenttype": "application/json",
"data": {
"id": "0da2b5ba-b92f-42bd-b9d2-0fcd978fec85",
"action": "UPDATE",
"type": "Event.Sport.Golf.BallHoled",
"created_at": "2026-04-24T11:09:15.267Z",
"sport_event": {
"id": "sr:match:67607764"
},
"payload": {
"event_time": "2026-04-24T11:09:15.267Z"
......... // event specific data
}
}
}{
"specversion": "1.0",
"id": "0da2b5ba-b92f-42bd-b9d2-0fcd978fec85",
"source": "/tournaments/1971",
"type": "Event.Sport.Golf",
"time": "2026-05-04T14:23:01.123Z",
"tournamentid": 1971,
"datacontenttype": "application/json",
"data": {
"id": "0da2b5ba-b92f-42bd-b9d2-0fcd978fec85",
"action": "DELETE",
"created_at": "2026-04-24T11:09:15.267Z",
"sport_event": {
"id": "sr:match:67607764"
}
}
}