Fixture Action
Name | Type | Description |
---|---|---|
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 | 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 . |
clockTime | String | The value on the clock when the action was collected. |
fixtureId | UUID | The unique id of the fixture. |
timestamp | String | of when the season is scheduled to start, in RFC 3339 format. |
sendTypeId | Integer | the send type . |
fixtureSeqNum | Integer | A deduplicated list of scorer sequence numbers based on the action creation time across all devices and all scorers. |
timelineSequence | Double | 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. |
relatedFixtureActionIds | String | The sub action type name. |
delayStatus | String | Identify delayed packets collected offline due to scorer disconnection, ensuring these packets include the actual collection timestamp upon reconnection. |
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
Last updated