Skip to main content

Allow or revoke a game for this casino

PUT 
/admin/games/:id

A PUT with a boolean rather than a POST and a DELETE: the control is a switch with two positions, and an idempotent write survives a double click without inventing a conflict.

Visible on the server-to-server catalog immediately. That catalog is cached briefly across the instance's processes, and this route drops the cache on write rather than leaving it to expire.

allowed is required. Omitting it is a 400 and never a revoke — switching a game off by omission is the one outcome a caller who forgot the field certainly did not intend.

Permission: games.write

Request​

Responses​

Saved, with the entry as it now stands