statshawk
REST APITeams

`GET /v1/teams/{team_id}` — assembled team row.

cost 1 unitany plan
GET
/v1/teams/{team_id}

Authorization

api_key
X-API-Key<token>

In: header

Path Parameters

team_id*string

Minted team id (team_…)

Response Body

application/json

application/json

curl -X GET "https://example.com/v1/teams/string"
{
  "data": {
    "home_competition": "comp_0a1b2c3d4e5f6g7h8i9j0k1l2m",
    "id": "team_0a1b2c3d4e5f6g7h8i9j0k1l2m",
    "name": "string",
    "sport": "basketball",
    "traits": [
      {
        "country": "BRA",
        "kind": "represents_country"
      }
    ]
  },
  "meta": {
    "cache": "HIT",
    "fetched_at": "2025-10-15T18:30:00Z",
    "request_id": "266ea41d-adf5-480b-af50-15b940c2b846",
    "source": "postgres",
    "version": "v1"
  }
}
{
  "error": {
    "code": "string",
    "message": "string",
    "property1": null,
    "property2": null
  }
}

`GET /v1/teams/{team_id}/stats?competition=&season=` — the materialized GET

season aggregate (Workflow-1 task A2). Store-only: the typed season tables are served directly, never a provider fan-out.

`GET /v1/teams` — the team index, filtered by sport / competition / team GET

trait and paged. Store-only: a flat table read scoped by the resolved filter, never a provider fan-out.