---
title: "Accept a match challenge"
method: POST
path: "/matches/{matchId}/challenges/accept"
tags: ["My Matches"]
---

# Accept a match challenge

`POST /matches/{matchId}/challenges/accept`

Accepts a pending challenge as the personal API key owner. The owner must be a captain, co-captain, or org owner of the challenged team and the proposed roster must satisfy existing match rules. Requires matches.user_matches:read-write and API writes access. Supports an optional `Idempotency-Key` header for safe retries.

## Path parameters

- `matchId` string, required — Match ID.

## Request body

- AcceptChallengeRequestBody — Accepts a pending challenge as the API key owner.
  - `activeRoster` string[], required — Active roster user IDs for the challenge response.
  - `benchRoster` object[] — Optional bench roster users.
    - `id` string, required — Bench user ID.
    - `priority` number, required — Bench priority.

## Response `200`

The challenge was accepted successfully.

- AcceptChallengeResponse
  - `success` true, required
  - `timestamp` string, required — Response generation 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.
- `500` — Internal server error.

---

[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/versions/2ffe8fb53b7d/schema)