This type of message is sent when changes are made for the team formation in the event with the ‘has_formation=yes’ parameter e.g. The "4-4-2" formation was changed to “4-5-1” formation etc.
Please note:
This type of message is only sent to STATSCORE partners with access to extended statistics.
Message example:
{
"id":35375806,
"uuid":"758d1ccd-0621-4683-9787-c2fbb199928f",
"type":"team_formation",
"source":1,
"ut":1641820987,
"data":{
"eventformationinfo":{
"id":1822556,
"sport_id":5
},
"teamformation":{
"id":51448,
"old_formation":"4-4-2",
"new_formation":"4-5-1"
}
}
}
Message structure details:
.message | |
|---|---|
id | Unique identifier for the message |
uuid | Universally unique identifier |
type | team_formation |
source | Internal attribute |
ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP |
..data | |
...eventformationinfo | |
id | Identifier of the event in which change was made |
sport_id | Identifier for the sport in which the event is played. The list of available sports you can find in API service method: sports.index |
...player | |
id | Unique identifier of the team (participant, type: team) in which change was made. The list of available participants you can find in API service method: participants.index |
old_formation | The old team formation |
new_formation | The new team formation |