Fixture Action

period integer	The period id.
actionId UUID	The id number of the action. This will be useful in linking actions that are pending, updated etc.
metadata Metadata	Provides essential contextual information about a sports event, including the coverage level, fixture status, collection status, and reason codes for collection status. This parameter enhances the data's utility by indicating the depth of event coverage, the real-time progress of the fixture, the current state of data collection, and explanations for any collection interruptions.
sendType string	the send type . Note that Pending actions can be cancelled. Confirmed actions can be deleted and typically all key actions (card, goal, penalty) start with a pending state. Please also note that "Updated" is not only used for actions that have been deleted. It also used for any change of players or sub types or anything else regarding a previously "Confirmed" action
clockTime string	The value on the clock when the action was collected.
fixtureId UUID	The unique id of the fixture.
timestamp timestamp	of when the season is scheduled to start, in RFC 3339 format.
sendTypeId integer	the send type .
fixtureSeqNum boolean	A deduplicated list of scorer sequence numbers based on the action creation time across all devices and all scorers.
timelineSequence	The timeline sequence
fixtureActionType string	The action type . Full list of actions can be found here.
fixtureActionTypeId integer	The action type Id related to the fixtureActionType.
fixtureActionSubType string	The sub action type name.
fixtureActionSubTypeId integer	The sub action type id related to fixtureActionSubType.
team Team	Team details
player optional Player	Player information

Information on fixtureSeqNum and timelineSequence

fixtureSeqNum is a deduplicated list of scorer sequence numbers based on the action creation time across all devices and all scorers. timelineSequence is a value that considers the chronological order of actions. The intention is for it to be both sequential and unique, ensuring that no actions have the same timelineSequence and that any action occurring afterward has a greater timeline sequence. When a fixture is finished the order of actions is based on the timelinesequence. During a live match, the packets should be ordered by fixtureSeqNum.

Sample Payload

"fixtureAction": {
  "period": 1,
  "actionId": "6ee3f4f6-e85c-448a-a13a-f5b85979337f",
  "sendType": "Confirmed",
  "clockTime": "10:00",
  "fixtureId": "2104e2e1-3439-4684-a146-28df3f89bda2",
  "timestamp": "2022-09-25T14:20:57.092100Z",
  "sendTypeId": 5,
  "fixtureSeqNum": 11,
  "timelineSequence": 1.000000000000001,
  "fixtureActionType": "Red Card",
  "fixtureActionTypeId": 105,
  "fixtureActionSubType": "Straight Red",
  "fixtureActionSubTypeId": 10501,
  "team": {
    "homeTeam": true,
    "id": "867a43cd-140d-4792-a7b0-74eefca2527f",
    "name": "KV Kortrijk"
  },
  "player": {
    "id": "ac367f4c-c8a5-48ac-afdc-be9fbddfa60c",
    "name": "Kristof D'Haene"
  }
}