Skip to main content

Check a game restriction

POST /api/v1/restrictions/check

Use POST so scoped identifiers do not appear in query strings, browser history, or ordinary proxy URL logs.

{
  "game_id": "game_ab12cd34",
  "scoped_user_id": "51028391"
}

Not restricted​

{
  "restricted": false,
  "restriction": null
}

Restricted​

{
  "restricted": true,
  "restriction": {
    "action": "ban",
    "reason": "Repeated targeted harassment",
    "caseId": "GDN-2026-000184",
    "createdAt": "2026-07-17T14:03:00.000Z",
    "expiresAt": null
  }
}

The check is game-scoped. Never reuse an identifier from one game to query another game.

Continuity​

Restriction checks continue after subscription expiry. Report evidence and restrictions have separate retention:

  • old report text may be deleted according to the workspace retention setting;
  • the restriction keeps its scoped identifier, game, reason, case reference, dates, and status;
  • it remains effective until its own expiry, revocation, workspace deletion, or a documented retention decision.

Studios should review indefinite restrictions periodically and keep an appeal/revocation process. A CSV export is available from the dashboard for independent continuity.