competitor resource powers every team-scoped view in V1. Team data is embedded inline in scores/standings, plus there are two dedicated endpoints for schedules.
Endpoints
| Endpoint | Returns |
|---|---|
GET /api/v1/competitor/{id}/games | Upcoming + recent games for one team. |
GET /api/v1/competitor/{id}/results | Past results, paginated, with competitionFilters[]. |
GET /api/v1/{sport}/competitor/{id}/games.
Sample
?competitionId={id}.
Team identity fields
Anywhere a team appears (standings, scores, lineups), expect these keys:| Field | Notes |
|---|---|
id | Stable team ID — use as your foreign key. |
name / shortName / symbolicName | ”FC Barcelona” / “Barcelona” / “BAR”. |
nameForURL | URL-safe slug. |
color / awayColor | Brand hex colors for badges. |
mainCompetitionId | The league the team’s primarily playing in. |
hasSquad / hasTransfers | Capability flags. |
imageVersion | Cache-buster for the logo URL. |
Logos
Related
- Competitions — list teams via standings.
- Head-to-Head — compare two teams directly.
- Search — resolve “Real Madrid” to ID 131.