---
title: "Revoke a tournament invite"
method: POST
path: "/tournaments/{identifier}/invites/{inviteId}/revoke"
tags: ["Tournament: Staff & Invites"]
---

# Revoke a tournament invite

`POST /tournaments/{identifier}/invites/{inviteId}/revoke`

Revokes a PENDING team invite. Requires the tournaments invites capability and ADMIN authority - the same floor as issuing one, because in an INVITE_ONLY tournament the invite is the entry gate; a tournament MODERATOR answers 403 but can still read the invite list. Answers 400 error_invalid_input when the invite is not pending: an already-accepted team is a participant, so remove them with the participant removal endpoint instead. No notification is sent - the invite simply disappears for the team.

## Path parameters

- `identifier` string, required — Tournament slug.
- `inviteId` string, required — Tournament invite ID.

## Response `200`

The invite was revoked.

- 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.

---

[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)