Overview

Returns a player's match-by-match performance history, including the match context, clubs and score, participation status, playing time, goals, cards, duels, and distribution statistics. Use it to build a player's game log or analyze individual match contributions across seasons.

Inputs

id (string, optional): Transfermarkt player ID. Defaults to 68290 in the endpoint definition. Example: 68290.
season_id (query parameter, optional): Available query key for filtering the upstream request by season when supported.

Response

The success response has the following verified shape:

success (boolean): true on success.
message (string): Response message, observed as OK.
data.playerId (string): Requested player ID.
data.performance (array): Match-performance records. Each record contains:
gameInformation: game ID, competition and season IDs, game day, duration, date, state, referee, stadium, and season labels.
clubsInformation: the player's club and opponent, including venue, club/coach IDs, goals, ranks, tactics, and points.
statistics.generalStatistics: shirt number, captain flag, participation state, position, injury/absence IDs, primary club, age, and points on the pitch.
statistics.goalStatistics: goals, assists, scorer value, own goals, team totals, penalty events, and scoring-attempt fields.
statistics.cardStatistics: yellow-card and fair-play values.
statistics.playingTimeStatistics: played minutes, starting status, and substitution details when present.
statistics.duelStatistics: tackle, foul, and offside fields.
statistics.distributionStatistics: pass, corner, throw-in, and goal-kick fields.
data.clubIds (array): Club IDs referenced in the performance history.
data.coachIds (array): Coach IDs referenced in the history.
data.competitionIds (array): Competition IDs referenced in the history.
data.gameIds (array): Game IDs referenced in the history.

Many statistic fields are null when the player did not participate or the source has no value. The performance array can be large.

Auth & browser

Authentication is not required. The endpoint does not require browser context or fetch mode.

Examples

Request

{
  "id": "68290"
}

Success response (trimmed from a verified request)

{
  "success": true,
  "message": "OK",
  "data": {
    "playerId": "68290",
    "performance": [
      {
        "gameInformation": {
          "gameId": "4810786",
          "competitionId": "BRA1",
          "seasonId": 2025,
          "gameDay": 28,
          "gameDuration": 90,
          "gameState": "regularly_terminated",
          "date": {
            "dateTimeUTC": "2026-09-19T21:30:00+00:00",
            "isTimeDefined": true
          }
        },
        "clubsInformation": {
          "club": {
            "venue": "away",
            "clubId": "221",
            "goalsTotal": 2,
            "opponentGoalsTotal": 1,
            "points": 3
          },
          "opponent": {
            "venue": "home",
            "clubId": "10997",
            "goalsTotal": 1,
            "opponentGoalsTotal": 2,
            "points": 0
          }
        },
        "statistics": {
          "generalStatistics": {
            "shirtNumber": null,
            "isCaptain": false,
            "participationState": "injured",
            "injuryId": 299,
            "primaryClubId": 221,
            "age": 34
          },
          "playingTimeStatistics": {
            "playedMinutes": null,
            "isStarting": false
          }
        }
      }
    ],
    "clubIds": ["5", "11", "3504", "3505", "82755", "91427"],
    "coachIds": ["40", "65", "9735", "9897", "138420", "148858"],
    "competitionIds": ["17WC", "2SAM", "CS", "ES1", "USC", "WMQ4"],
    "gameIds": ["939076", "939079", "3047871", "3047886", "5025588", "5025593"]
  }
}

Notes

The verified response contained a very large performance history; the example is intentionally trimmed.
Records include matches where the player was injured or not in the squad, so participation and playing-time fields should be checked before interpreting performance statistics.
Match, club, coach, competition, and game ID arrays provide convenient indexes for related lookups.
season_id is exposed as an available query key, but the verified request used only the default player ID.