Error reference

The request was malformed — a missing/invalid field, a bad slot/board/key name, or non-JSON body.

No valid credential. A game-scoped call needs the publishable key; a player-scoped call also needs a player token.

Authenticated but not allowed — e.g. a banned player, or Turnstile is required for a new anonymous player.

The browser Origin isn't in the game's allowed_origins. The classic 'works locally, 403s once deployed' trap.

A Triggair operator has suspended this game (a Terms-of-Service or abuse review). A valid key still resolves, but no game-scoped call proceeds.

The action conflicts with current state — e.g. a handle already taken, a friendship you've blocked, or a daily reward already claimed today.

An optimistic-concurrency (OCC) save conflict: the slot's version changed since you read it (a lost race or a stale If-Match).

The resource doesn't exist for this caller — an empty save slot, an unconfigured/disabled board, or a game/id you don't own.

The body exceeds a limit — a save > 256 KB, a config > 64 KB, or a share context > 4 KB.

A plan limit was hit — save slots (3 on free), the monthly-active-player cap, or another metered ceiling.

A wallet spend was denied because the balance would go negative. Balances never go negative — the whole transaction rolled back (you did not spend and fail to receive).

A grant or spend referenced a currency that isn't defined for this game. Currencies are explicit definitions — there is no implicit create.

A grant, consume, or store listing referenced an item that isn't in the game's catalog. Items are explicit definitions — there is no implicit create.

A consume/spend asked for more of an item than the player owns. Inventory quantities never go negative — the whole transaction rolled back.

The player already bought this listing up to its per-player purchase_limit.

The store listing's global stock is exhausted.

This loot table isn't live — it hasn't been enabled with the required compliance acknowledgement (loot boxes touch gambling/age regulation).

The player doesn't have enough energy/lives for this action. Energy regenerates over server time (never the client clock).

This item can't be gifted — only items defined as tradable move between players.

No active feature flag with that key (it's undefined or turned off). Unknown flags are expected — the SDK resolves them to the caller's safe default.

A segment's rule tree failed validation — an unknown predicate/operator, a bad value type, or too deep/large a tree.

No promo code with that string exists in this game (typo, or a never-minted code).

The code's redemption window has closed (server time), or the code/campaign is disabled.

This player already redeemed this code (per-player limit reached).

The campaign hit its total redemption cap — no more rewards remain.

The code is restricted to a player segment this player isn't a member of.

A quest was claimed before its objectives were met. Progress is a server-side projection over the stat store — the client can't assert completion.

A join was attempted before the tournament's registration window opens (server time, §4.10).

The tournament has ended — joins and submissions are closed. Prizes (if any) are already in the winners' inboxes.

A battle-pass tier was claimed before the player earned enough battle points to reach it.

A premium-lane battle-pass reward was claimed but the player doesn't own the premium pass.

A turn was submitted to an async match when it wasn't that player's turn.

An async-match turn lost the optimistic-concurrency check — the `version` didn't match the current one (another turn landed first).

The player's team role doesn't permit this action (or they aren't a member) — e.g. a non-admin kicking, a non-owner disbanding, or the owner trying to leave.

The player is already in the maximum number of teams allowed.

The player is banned from this team (by an admin/owner) and cannot join by any path — open join, invite-accept, or request-approve.

An optimistic-concurrency write to a storage document lost the race — the `If-Match` version didn't match the current one (the multi-tab/multi-device lost-update guard).

A player token tried to write a storage document its policy doesn't allow — e.g. authoritative shared/world state (write_policy: server, the fail-closed default).

This reporter already has an open report against the same target.

This player filed too many reports within the hour (per-player abuse control).

This account or device is banned from the game, so no player token is issued.

This ban's appeal was already granted or denied.

This player's age bracket isn't established, so every regulated feature (loot boxes, real-money IAP, open chat, public UGC) fails closed to the most-restrictive treatment.

This feature isn't available to this player's age group in their region, and no parental consent can unlock it.

A minor may use this feature only with verifiable parental consent (VPC), which hasn't been requested yet.

Parental consent has been requested for this minor but the parent hasn't decided yet.

Too many requests — the global token bucket or a per-board submission cap. A `Retry-After` header (and X-RateLimit-*) tells you when.

An unexpected server error. Rare and transient.