Apply and query player sanctions using EOS Sanctions Web API
domain: dev.epicgames.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate server-side using client credentials to obtain an EOS deployment-scoped access token
POST to the Sanctions Web API to create a new sanction, supplying the target player's PUID, action (e.g., ban or mute), duration in seconds, and a reference reason string
Poll or query active sanctions for a player by sending a GET request to the sanctions endpoint filtered by PUID to confirm the sanction is in effect
Integrate the sanction check into your session join flow so banned players receive an appropriate rejection before matchmaking
Handle sanction expiry by periodically querying and updating your local cache rather than relying solely on client-side state
Known gotchas
Sanctions are deployment-specific; a sanction applied in your staging deployment does not carry over to production
The EOS SDK's local EOS_Sanctions_QueryActiveSanctions call only returns sanctions already cached; call the Web API from your backend for authoritative real-time checks
Permanent bans require a duration value of 0; omitting the field defaults to a short temporary restriction in some SDK versions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?