---
title: "Filterable per-game log for a player"
method: GET
path: "/v1/players/{id}/game-log"
tags: ["players"]
---

# Filterable per-game log for a player

`GET /v1/players/{id}/game-log`

## Request

- Base URL: `https://api.bigballsdata.com`
- URL: `https://api.bigballsdata.com/v1/players/{id}/game-log`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Game-by-game log with filters. DISTINCT from GET /v1/players/{id}/gamelog, which is a separate route with its own query schema. This one supports opponent/venue/result filtering and pagination.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `season` integer
- `opponent` string
- `venue` 'home' | 'away'
- `result` 'W' | 'L'
- `sort` 'date_asc' | 'date_desc'
- `limit` integer
- `offset` integer

## Response `200`

ok.

- object
  - `data` object, required

## Other responses

- `400`: Invalid player id or query (e.g. limit above 100).
- `404`: No player with that id.

---

[API](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api.md) · [All operations](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/revisions/31fb54ac414e?raw)