---
title: "Override a bracket node result"
method: POST
path: "/tournaments/{identifier}/nodes/{nodeId}/override-result"
tags: ["Tournament: Bracket & Results"]
---

# Override a bracket node result

`POST /tournaments/{identifier}/nodes/{nodeId}/override-result`

## Request

- Base URL: `https://teambattles.gg/api/v1`
- URL: `https://teambattles.gg/api/v1/tournaments/{identifier}/nodes/{nodeId}/override-result`
- Auth: HTTP bearer

Applies an organizer-decided result to a bracket node and advances the bracket. Requires the tournaments bracket capability and ADMIN authority on the tournament - a tournament MODERATOR answers 403. The result must be decisive: the scores may not be equal, and one side must reach the node's winsNeeded (ceil(bestOf / 2)); a winning score above winsNeeded is accepted. Answers 400 error_invalid_input when the node is not READY or IN_PROGRESS, when either entrant is missing or disqualified, when the linked match has already started, or when the scores are not a decisive pair of non-negative integers.

## Path parameters

- `identifier` string, required: Tournament slug.
- `nodeId` string, required: Bracket node ID.

## Request body

- TournamentOverrideNodeResultBody: Bracket node result override payload.
  - `score1` integer, required: Score for the node's first entrant.
  - `score2` integer, required: Score for the node's second entrant.

## Response `200`

The result was applied and the bracket advanced.

- 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.
- `409`: Conflict.
- `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/nodes/:nodeId/override-result/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)