Versions Compared

Version Old Version 2 New Version 3
Changes made by

Dinyo Dyankov

Dinyo Dyankov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

Feed Match Event

Ably LiveAccess can be obtained via:

Pull APIs:

IMPORTANT: All enums should be considered extensible, meaning any additional values beyond the ones explicitly defined should be accepted.

Volleyball Match Events example:

View file
namematchevents-v1-GeniusSportsItaly-11629093.json

Code Block
languagejson
{
  "sportId": 91189,
  "fixtureId": "123456789",
  "source": "SourceName",
  "sequenceId": 1,
  "actionId": 0,
  "insertedBeforeActionId": null,
  "isCancelled": false,
  "isConfirmed": true,
  "isModified": false,
  "action": {},
  "messageTimestampUtc": "2024-11-18T10:52:29.0262167Z"
}

Element

Type

Description

sportId

integer

Sport identifier

fixtureId

string

Fixture identifier

source

string

Feed provider identifier

sequenceId

integer

Fixture-specific sequence identifier of the match event

actionId

integer

Match action identifier

isCancelled

boolean

Indicates whether the action is cancelled

isConfirmed

boolean

Indicates whether the action is confirmed

isModified

boolean

Indicates whether the action is modified

action

{}

Consists of Match Action data properties

messageTimestampUtc

string($date-time)

Timestamp of the message

Every Match Event has a type inside the “action” field, named after the respective Action. Example for Point below, where Point is replaced for different Actions.

Code Block
languagejson
"action": {
    "$type": "GeniusSports.MatchState.Platform.MatchEvents.Volleyball.Point, GeniusSports.MatchState.Platform.MatchEvents.Volleyball"
}

Feed Match Action