Pular para o conteúdo principal

The active casino's battles, newest first

GET 
/admin/battles

Read-only, plus one write. Opening a battle is the casino backend's act over the server-to-server API — it carries a player reference, a wallet and a settlement, none of which exist inside an operator's session. What an operator does here is diagnose, and close a lobby that got stuck open.

The list is capped rather than paginated by cursor: the truncation is visible, because a client that receives exactly limit rows knows it is looking at the most recent ones.

An unknown status is a refusal, not an empty list — a mistyped filter that answered zero rows looks exactly like a casino with no battles.

Permission: battles.read

Request​

Responses​

The battles