Submit a player report via Epic Online Services Player Reports 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
Obtain a client credentials access token from the EOS Auth endpoint using your deployment client ID and secret
Construct a POST request to the Player Reports Web API endpoint with the reporter's product user ID, the reported player's product user ID, reason category, and message body
Include the Authorization header with the bearer token and set Content-Type to application/json
Parse the response to confirm the report was accepted; handle 400-series errors indicating invalid product user IDs or missing required fields
Store the returned report ID for audit trails and downstream moderation workflow correlation
Known gotchas
EOS player report tokens are scoped to a deployment; using a token from the wrong deployment returns a 403 even if credentials are otherwise valid
The reporter and reported player IDs must be product user IDs (PUIDs), not account IDs — mixing them causes silent validation failures
Player Reports Web API requires server-side calls only; never expose the deployment client secret in game client code
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?