Documentation Index
Fetch the complete documentation index at: https://teambattles.gg/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
TeamBattles supports two score submission flows:- Captain Score Submission - Team captains submit scores on behalf of their team
- Game Developer Score Submission - Game servers submit verified scores directly
Captain Score Submission
Captains submit scores for their team. The opposing team must confirm the score.Submit Score
| Field | Type | Required | Description |
|---|---|---|---|
mapIndex | number | Yes | Zero-based map index |
mapId | string | Yes | Map identifier string |
creatorTeamScore | number | Yes | Creator team’s score (>= 0) |
opponentTeamScore | number | Yes | Accepted team’s score (>= 0) |
screenshotUrls | string[] | No | Array of screenshot URLs |
Confirm Score
The opposing team’s captain confirms a submitted score using PATCH on the same endpoint.Get Scores
Retrieve all map scores for a match, including series score summary.Game Developer Score Submission
Requires Game Developer approval for the specific game. Scores submitted via this endpoint are
automatically confirmed.
Submit Verified Score
Key Differences
| Feature | Captain Submission | Game Developer Submission |
|---|---|---|
| Authentication | User API key | Game developer API key |
| Auto-confirmation | No (requires opponent) | Yes |
| Metadata support | No | Yes |
| Game scope | Any | Approved games only |
| Permission required | matches.team_matches: read-write | game.scores: write |