- Starting lineup formation
- End-of-match formation
- Average player locations
- Player metadata (name, number, position)
- Formation analysis for different match intervals
- Tactical analysis
- Formation visualization
- Broadcast graphics
- Match reports and dashboards
Parameters
Module API fixed and cannot be changed. Always use
api.Endpoint name. Use
MatchFormation.API version. Use
V2.Unique identifier of the match.
Team side for which the formation is requested. Possible values:
home or away.Language of returned names. Supported values:
en, ar.Output format (
json or xml).API authentication key.
Example Request
Response Structure
Formation Information
| Field | Description |
|---|---|
| matchId | Unique match identifier |
| matchName | Match name including teams and score |
| teamId | Team identifier |
| teamName | Team name |
| lineupFormationName | Formation used at kickoff |
| endOfMatchFormationName | Formation detected at the end of the match |
Player Average Location
Each player object includes their average position on the pitch during the analyzed period.| Field | Description |
|---|---|
| intPlayerID | Unique player ID |
| strNickNameEn | Player display name |
| intShirtNumber | Shirt number |
| strPositionEn | Tactical position |
| location.x | Horizontal coordinate on the pitch |
| location.y | Vertical coordinate on the pitch |
- X axis:
0 → 100(goal to goal) - Y axis:
0 → 100(left to right across the field)
Formation Intervals
The response may include formation analysis for different time segments of the match:1st Half2nd Half1st Half Q11st Half Q21st Half Q32nd Half Q12nd Half Q22nd Half Q3
Typical Use Cases
The formation data can be used to build:- Average position maps
- Tactical shape visualizations
- Heatmaps of player positioning
- Broadcast tactical overlays
- Post-match analysis reports