Race / Event Endpoints

Scoring Format

Motorsport uses finishing positions rather than traditional scores. A race weekend and each of its sessions are stages, and the stage payload identifies the winner only.

{
  "stage": {
    "id": 214146,
    "description": "Grand Prix",
    "status": { "description": "Finished", "type": "finished" },
    "winner": {
      "name": "George Russell",
      "shortName": "G. Russell",
      "nameCode": "RUS",
      "parentTeam": { "name": "Mercedes", "id": 214902 }
    },
    "circuitCity": { "name": "Melbourne", "country": { "alpha2": "AU" } },
    "startDateTimestamp": 1741694400
  }
}

There is no per-driver classification on Motorsport V2. Verified end to end (August 2026): the weekend stage, every session sub-stage, and every sub-route return winner and nothing more. There is no results[] array, no positions 2–N, no gaps, no lap times, no grid, no lap-by-lap data and no championship points per race. /results, /classification, /standings, /laps and /startgrid all return 404.If your use case is top-N settlement (podium, points finish, head-to-head between two drivers), Motorsport V2 cannot support it today. Only “who won” is settleable.

Championship tables are available at the season level: /api/motorsport/tournament/:uniqueStageId/season/:seasonId/standings and /standings/teams (both return constructor standings).

Race Weekend Sub-Stages / Sessions

A Grand Prix weekend is a parent stage (e.g. “Australian Grand Prix”). Each session inside the weekend — Free Practice 1/2/3, Qualifying, Sprint Qualifying (Sprint Shootout), Sprint Race, and the Race itself — is a child sub-stage with its own numeric matchId.

Two-step workflow

1. List the sessions for a weekend:

GET https://api.sportsapipro.com/v2/motorsport/match/{weekendId}/substages
x-api-key: YOUR_API_KEY

Real response (Australia GP 2026, weekend stage 214141, trimmed):

{
  "success": true,
  "data": {
    "stages": [
      { "id": 214142, "description": "Practice 1", "status": { "type": "finished" }, "winner": { "shortName": "L. Norris" } },
      { "id": 214143, "description": "Practice 2", "status": { "type": "finished" } },
      { "id": 214144, "description": "Practice 3", "status": { "type": "finished" } },
      { "id": 214145, "description": "Qualification", "status": { "type": "finished" } },
      { "id": 214146, "description": "Grand Prix", "status": { "type": "finished" }, "winner": { "shortName": "G. Russell" } }
    ]
  }
}

The session label is in description. Observed values: Practice 1, Practice 2, Practice 3, Qualification, Sprint Qualification, Sprint, Grand Prix. Match on substrings rather than exact strings — labels vary by championship. 2. Fetch detail for a specific session using its id:

GET https://api.sportsapipro.com/v2/motorsport/match/{sessionId}

The session payload carries description, status, winner, stageParent, circuitCity, country, info and timestamps — no per-driver classification (see the warning above). GET /api/match/{sessionId}/highlights also works per session where a highlight package is published (typically Qualifying, Sprint, and Race — not usually Practice).

Upstream Limitations

The following sub-endpoints are not available for motorsport — the upstream feed embeds this data inside the stage detail rather than exposing dedicated routes. Requests return 404 by design (this is not a bug and is the same from every network):

GET /api/match/:matchId/scores
GET /api/match/:matchId/lineups
GET /api/match/:matchId/statistics
GET /api/match/:matchId/incidents
GET /api/match/:matchId/startgrid
GET /api/match/:matchId/player-statistics
GET /api/match/:matchId/player/:pid/statistics
GET /api/match/:matchId/best-players
GET /api/match/:matchId/graph
GET /api/match/:matchId/pregame-form
GET /api/match/:matchId/streaks
GET /api/match/:matchId/odds and /odds/all, /odds/pre-match, /odds/live
GET /api/match/:matchId/winning-odds
GET /api/match/:matchId/award
GET /api/match/:matchId/h2h
GET /api/match/:matchId/media
GET /api/match/:matchId/votes
GET /api/match/:matchId/missing-players
GET /api/match/:matchId/channels
GET /api/match/:matchId/venue

Use GET /api/match/:matchId (Race Details) instead — it carries the stage metadata and the winner. Per-driver classification, grid, lap data and race incidents are not published at all for motorsport. This is a permanent upstream limitation, not a bug.

Confirmed working sub-endpoints for motorsport

GET /api/match/:matchId — race/stage detail (metadata + winner only)
GET /api/match/:matchId/highlights — video highlights