Choose and implement the right Epic Online Services login flow — Epic Account (Auth interface) versus anonymous Device ID (Connect interface) — for a given platform
domain: dev.epicgames.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the Auth interface (EOS_Auth_Login) when you want a full Epic Games account with automatic token refresh, cross-title identity, and Anti-Cheat eligibility.
Use the Connect interface's EOS_Connect_CreateDeviceId plus EOS_Connect_Login when you need frictionless anonymous play (common on mobile) without prompting for credentials.
After creating a device-based Connect identity, prompt the player to link an external account via EOS_Connect_LinkAccount once they hit a progression milestone, so device-only progress isn't lost if the device is wiped.
Remember that Connect-interface JSON Web Tokens must be refreshed manually by the game, unlike Auth-interface sessions which refresh automatically.
Remember Device ID accounts cannot be used with the EOS Anti-Cheat interfaces, which require an externally verified account.
Known gotchas
Losing a Device ID's local storage (reinstall, new device) permanently loses that identity's progress unless it was linked to a real account first.
Auth and Connect are separate identity systems; a Product User ID from Connect is not automatically the same as an Epic Account ID from Auth without an explicit link step.
Anti-Cheat-enabled titles must gate Device ID-only sessions or require account linking, since Device ID users can't be protected by EOS Anti-Cheat.
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?