...
You can receive this information through endpoints events.show and events.index
The event details parameter "Has formations" informs about the availability of formation for the match and can be found in the following node:
competition → season → stage → group → event
...
"id": 178,"name": "Has formations","value": "yes",
If the “Has formation” parameter’s value is equal to:
“no”, formations are not available for the chosen event
“soon”, formations will be available for the chosen event in the next few minutes
“yes”, formations are available for the chosen event
Please , be informed that it may take a short while for a scout to enter the proper formation. If you receive no data, recheck in a couple of minutes.
Team’s formation for selected match
...
"id": 716,"short_name": "Form.","name": "Form.","value": "4-4-2","data_type": "text"
Assigning players to positions for the formation in
...
a match
Depending on the selected formation, the player may assume take different positions on the field. Their exact location is graphically presented in the table below and is the same as the "Player's position" statistic assigned to a the player. The “Players position” statistics are available through events.sub-participants.index endpoint.
...
"id": 717,"name": "Player's position","short_name": "P. position.","value": 11,"data_type": "integer"
PUSH information about changes in the team formation or players positions
For STATSCORE partners using AMQP, it is also possible to receive PUSH messages informing about:
changing the team formation
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.
More information about the message structure is available here: Integration guide → AMQP service → Messages types → Message: team_formationchanging the player's position in the team formation
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.
More information about the message structure is available here: Integration guide → AMQP service → Messages types → Message: player_position
Formations
| Info |
|---|
Please |
...
be informed that for each formation, the players' position values are numbered from 1 to 11, and |
...
are always assigned |
...
starting from the goalkeeper and then successively, from the right to the left side of the field |
...
Formations
We are currently using 12 17 different formations with the player’s players' positions listed in the table below:
Formation | Player’s position | |||
|---|---|---|---|---|
| 1 | 4-4-2 |   | ||
| 2 | 4-3-3 |   | ||
| 3 | 3-4-3 |   | ||
| 4 |  | 5 | 3-4-2-1 |   |
| 65 | 4-5-1 |   | ||
| 76 | 5-2-2-1 |   | ||
| 87 | 3-5-2 |   | ||
| 98 | 4-3-1-2 |   | ||
| 109 | 4-2-3-1 |  | 11 | 4 |
| 10 | 4-4-1-1 |  | ||
| 11 | 5-3-2 |  | ||
| 12 | 3-4-1-2 |
| ||
| 13 | 4-1-4-1 |  | ||
| 14 | 4-3-2-1 |   | ||
| 1215 | 54-1-3-2 |   | ||
| 16 | 4-2-2-2 |  | ||
| 17 | 5-4-1 |  |
