---
title: "Forfeit a match on behalf of one participating team"
method: POST
path: "/game/matches/{matchId}/forfeit"
tags: ["Game: Matches"]
---

# Forfeit a match on behalf of one participating team

`POST /game/matches/{matchId}/forfeit`

Forfeits the match for the supplied team; the other participating team wins. Valid only while the match is ACCEPTED, READY, or IN_PROGRESS. Requires the game.lifecycle:read-write permission and a key bound to the match's game. Supports an optional `Idempotency-Key` request header: a retry with the same key and body replays the original response, while the same key with a different body returns 409 error_idempotency_key_conflict.

## Path parameters

- `matchId` string, required — Match ID.

## Request body

- GameForfeitBody — Request body for forfeiting a match on behalf of one participating team.
  - `forfeitingTeamId` string, required — ID of the team that forfeits. Must be a participant of the match.
  - `reason` string — Optional human-readable forfeit reason, recorded on the match.

## Response `200`

The match was forfeited successfully.

- GameForfeitResponse — Result of a successful match forfeit.
  - `success` true, required
  - `matchId` string, required — ID of the forfeited match.
  - `forfeitedByTeamId` string, required — ID of the team that forfeited.
  - `timestamp` string, required — Server response time (ISO 8601).

## Other responses

- `400` — Bad request (invalid body, cursor, limit, or date).
- `401` — Missing or invalid API key.
- `403` — API key lacks the required permission.
- `404` — Resource not found.
- `409` — Conflict.
- `429` — Rate limited.

---

[API](https://skmtc.net/teambattles/apis/teambattles-api.md) · [All operations](https://skmtc.net/teambattles/apis/teambattles-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/teambattles/teambattles-api/revisions/2ffe8fb53b7d/schema)