---
title: "Update match attendance"
method: POST
path: "/matches/{matchId}/attendance"
tags: ["My Matches"]
---

# Update match attendance

`POST /matches/{matchId}/attendance`

Updates the personal API key owner's own attendance status for a match. The owner must already be rostered in the match; the platform may swap active and bench players automatically. 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

- UpdateAttendanceRequestBody — Updates the API key owner's own attendance status for a match.
  - `status` 'ATTENDING' | 'NOT_ATTENDING' | 'TENTATIVE', required — The API key owner's attendance status for this match.

## Response `200`

The attendance status was updated.

- UpdateAttendanceResponse
  - `success` boolean, required
  - `reclaimedSpot` boolean
  - `replacedBy` string
  - `message` string
  - `timestamp` string, required

## 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/revisions/2ffe8fb53b7d/schema)