---
title: "Add a member to any participant's roster (organizer)"
method: POST
path: "/tournaments/{identifier}/participants/{participantId}/roster"
tags: ["Tournament: Registration"]
---

# Add a member to any participant's roster (organizer)

`POST /tournaments/{identifier}/participants/{participantId}/roster`

## Request

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

Adds a user to the named participant's tournament roster as the organizer. Requires ADMIN authority on the tournament - a tournament MODERATOR is NOT sufficient here, because editing any participant's roster carries the same weight as issuing an invite; a moderator edits only rosters for teams they lead, via the competitor roster endpoint. Answers 400 error_invalid_input when the user is not an active member of that team or is already rostered in this tournament. Requires the tournaments registration capability.

## Path parameters

- `identifier` string, required: Tournament slug.
- `participantId` string, required: Tournament participant ID.

## Request body

- TournamentOrganizerRosterAddBody: Organizer roster addition payload.
  - `userId` string, required: User ID of the member to add to the participant's roster.

## Response `200`

The member was added to the roster.

- 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/participants/:participantId/roster/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)