My Matches
Confirm A Map Score
Confirm a map score the opposing team submitted; only their opponent can confirm.
PATCH
Permission Required
This endpoint requiresmatches.team_matches:read-write on your API key. A free (api_free) key receives 403 error_api_feature_required; this requires an api_pro+ plan.
Access / Membership Rules
The confirmation is recorded as the API key owner, derived from the key itself - it is never accepted as a body field. Only the opposing team’s captain can confirm a score: a captain cannot confirm their own team’s submission. Confirming moves the map score fromPENDING to CONFIRMED (see Submit A Map Score). A personal key can only confirm scores for matches whose teams its owner captains - the route binding is a no-op and this authorization is enforced inside Convex. A non-personal key receives 403 API_KEY_PERMISSION_DENIED.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
mapIndex | number | Yes | Zero-based map index to confirm (non-negative integer). |
What’s Returned
Returnssuccess: true, action: "confirmed", the mapIndex, and scoreStatus: "CONFIRMED". Mintlify renders the full schema from the spec below.
Authorizations
Send your API key as: Authorization: Bearer tb_
Path Parameters
Match id.
Body
application/json
Confirmation payload identifying the map score to confirm.
Zero-based map index to confirm. Must be a non-negative integer.
Required range:
0 <= x <= 9007199254740991Response
Map score confirmed.
Result of submitting or confirming a map score.