End a battle that is under way
POST/admin/battles/:id/abort
The operator's way out of a battle that started and got stuck. It ends as
FAILED, never CANCELLED: a lobby nobody joined is cancelled, while a
battle with recordings in flight ended badly, and telling the casino
"cancelled" would describe a refund it is not getting.
Only STARTING and RUNNING are accepted. An OPEN lobby is a 409 and
belongs to /cancel; a battle that already ended is a 409 too, rather than
a no-op success that would claim the operator stopped something.
It goes through the lobby, so the terminal event is published and every connected viewer is told. Seats already in flight are not stopped — they die on their own deadline — and nothing is refunded: settlement is the consuming backend's, as it is for every other failure.
Permission: battles.write
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 503
Aborted, with the battle as it now stands
X-Tenant-Id is missing
No session cookie, or it expired
The role lacks battles.write, or the caller is not a member of this casino
No such battle for this casino
The battle is not STARTING or RUNNING
The lobby is not available on this instance