---
title: "Remove a member from your own team's roster"
method: DELETE
path: "/tournaments/{identifier}/teams/{teamIdentifier}/roster/{rosterEntryId}"
tags: ["Tournament Entry"]
---

# Remove a member from your own team's roster

`DELETE /tournaments/{identifier}/teams/{teamIdentifier}/roster/{rosterEntryId}`

## Request

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

Removes a roster entry from a team you lead. The entry must belong to BOTH the tournament and the team in the path; an entry from another tournament or another team answers 404 error_tournament_not_found, identically to one that does not exist, so this endpoint is not a cross-team existence oracle. Roster entry IDs come from GET /tournaments/{identifier}/me for your own entry, or from the participants endpoint for the rest of your team. Removing an entry sourced from the free-agent pool releases that player back to the pool as AVAILABLE - the step that must precede removing a picked-up agent from the pool. Requires the tournaments actor roster capability.

## Path parameters

- `identifier` string, required: Tournament slug.
- `teamIdentifier` string, required: Slug of the team to act as. You must be its captain, co-captain, or the owner of the organization that owns it. A team you do not lead and a slug that does not resolve BOTH answer 403 error_not_team_leader, so that this path is not a team-slug enumeration oracle.
- `rosterEntryId` string, required: Tournament roster entry ID.

## Response `200`

The roster entry was removed.

- 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/teams/:teamIdentifier/roster/:rosterEntryId/delete.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)