---
title: "Add or update a tournament staff member"
method: POST
path: "/tournaments/{identifier}/staff"
tags: ["Tournament: Staff & Invites"]
---

# Add or update a tournament staff member

`POST /tournaments/{identifier}/staff`

## Request

- Base URL: `https://teambattles.gg/api/v1`
- URL: `https://teambattles.gg/api/v1/tournaments/{identifier}/staff`
- Auth: HTTP bearer

Grants a user the ADMIN or MODERATOR staff role on the tournament. Requires the tournaments staff capability and ADMIN authority - strictly higher than the MANAGER floor for reading the roster, so a tournament MODERATOR answers 403 and cannot promote themselves. Upserts by user: posting a role for someone who already holds a staff row updates that row instead of creating a second one, so this endpoint is safely retryable and also serves as the change-role operation. A MODERATOR gains the manager-floor endpoints (application review, participant removal and disqualification, free-agent pool moderation) but none of the admin-floor ones.

## Path parameters

- `identifier` string, required: Tournament slug.

## Request body

- TournamentAddStaffBody: Tournament staff addition payload.
  - `userId` string, required: User ID of the staff member to add.
  - `role` 'ADMIN' | 'MODERATOR', required: Tournament staff role.

## Response `200`

The staff member was added or their role updated.

- TournamentWriteAck: Acknowledgement returned by the tournament write endpoints whose backing operation has nothing to return - the organizer writes (endpoints 22-34), the team roster writes (40, 41), and the competitor self actions that neither mint nor resolve a row (38, 39, 44, 45, 47). Endpoints that mint a row answer with that row's id instead, and the two respond endpoints (42, 46) answer with the decision they recorded.
  - `success` true, required: Always true; failures are error responses.
  - `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.
- `429`: Rate limited.
- `500`: Internal server error.

## Changes

- **2026-07-23** `33b122ff59d0`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/teambattles/apis/teambattles-api/changes/tournaments/:identifier/staff/post.md)

---

[API](https://skmtc.dev/teambattles/apis/teambattles-api.md) - [All operations](https://skmtc.dev/teambattles/apis/teambattles-api/llms.txt) - [OpenAPI document](https://skmtc.dev/teambattles/apis/teambattles-api/revisions/75b07daef7dc?raw)