Position history

• idpathRequired

  DataSportsAPI team id, a positive integer

• leaguequeryRequired

  league id, for instance one returned by /v2/teams/{id}/leagues

• seasonqueryRequired

  season id, as listed by /v2/leagues/{id}/seasons

The same call from the command line and each SDK. The SDK lines assume a client created with your key; left out, it is read from DATASPORTSAPI_API_KEY. Installing a client: SDKs & CLI.

curl -H "Authorization: Bearer dsa_live_…" \
    "https://api.datasportsapi.com/v2/teams/{id}/position-history?league=…&season=…"

The top-level keys of the JSON body. Each object links to its full shape in the data reference.

{ "data": [ { "week": 1, "from": "2026-08-21", "to": "2026-08-27", "position": 2, "fixtureIds": [201101] },
    { "week": 2, "from": "2026-08-28", "to": "2026-09-03", "position": 1, "fixtureIds": [201188] }, … ],
  "meta": { "league": 195828, "season": 200386, "count": 9 } }

• 400bad_request

  league or season is absent or malformed

• 403history_not_in_plan

  the season finished before your plan’s history window begins

• 404no_data

  the source holds no position history for this team, league and season (an id DataSportsAPI never assigned gives 404 not_found instead)

• 404not_found

  the season id does not belong to this league; the error message names the offending parameter, and /v2/leagues/{id}/seasons lists the valid ones