Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This type of message is sent when changes are made for the player position in the team formation in the event with the ‘has_formation=yes’ parameter e.g. The "Test Player" was corrected and positioned as a striker (position: 11), although the previously was positioned as a midfielder (position: 6) etc.

Info

Please note:

This type of message is only sent to STATSCORE partners with access to extended statisticsGOLD or VIP package.

Message example:

Code Block
languagejson
{
"id":35375803,
"uuid":"4f70dc1f-1af5-4563-972e-48fe3ef2ae38",
"type":"player_position",
"source":1,
"ut":1641820938,
"data": {
  "eventplayerpositioninfo": {
    "id":1822556,
    "sport_id":5
    },
  "player": {
    "id":51449,
    "lineup_id":15,
    "name":"Test Player",
    "position":"1st lineup",
    "team_id":51448,
    "player_position":3
    }
  }
}

...

.message


id

Unique identifier for the message

uuid

Universally unique identifier

type

player_position

source

Internal attribute

ut

Information about the date and time of when the message was created. Format UNIX_TIMESTAMP

..data


...eventplayerpositioninfo


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 player (participant, type: person) for whom the change was made. The list of available participants you can find in API service method: participants.index

lineup_id

Internal attribute

name

Participant name

position

Participant position. Available values:

  • 1st lineups

  • Bench

  • Coach

team_id

Unique identifier of the team (participant, type: team) to which the corrected player belongs. The list of available participants you can find in API service method: participants.index

player_position

The new player position in the team formation

...