Epic Games OSINT: Find Linked Gaming Accounts

Epic Games identities rarely exist in isolation. The same player may connect PlayStation Network, Xbox, Steam, or Nintendo accounts, use a creator code, and appear under several identifiers over time. That makes Epic Games a useful starting point for cross-platform gaming OSINT.

Osintly provides both a hosted Epic Games lookup and a documented Epic Games developer API. You can test an identifier manually, then move the same workflow into an application without rebuilding provider integrations.

Use these tools only for lawful, authorized investigations. Public or linked account data is evidence to review, not proof of a person's real-world identity.

What the Epic Games tool can search

The API accepts nine identifier types:

This matters because an investigation does not always begin with an Epic display name. A known console username or platform ID may be the best pivot into the Epic ecosystem.

Before writing code, open the hosted Epic Games tool. It is the quickest way to confirm the expected identifier type, inspect the output, and decide which API routes your product needs.

Start with search and suggestions

The search route validates and discovers likely candidates without consuming a tool credit. Suggestions are also available without a tool credit. These routes are useful for typeahead interfaces and for reducing failed paid lookups.

A production workflow should:

1. Normalize the supplied identifier.

2. Call search or suggestions.

3. Let the user select the intended candidate when several matches exist.

4. Resolve the candidate to a stable Epic account ID.

5. Request only the enrichment required by the case.

The current route list and credit cost for each operation are published in the Epic Games API reference.

Resolve a display name to an account ID

Display names can change. An account ID is a better internal key for storing results and comparing observations over time.

A typical server-side request uses your Osintly bearer token:

curl --request POST \
  --url https://api.osint.ly/tools/epic-games/resolve \
  --header "Authorization: Bearer $OSINTLY_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "identifier": "example_player",
    "identifier_type": "epic_display_name"
  }'

Check the live Epic Games documentation for the exact request and response schema before shipping. Keep API keys on your server and follow the authentication guidance.

Pivot into linked gaming accounts

The linked-accounts route costs one tool credit and is one of the most useful investigative pivots. Depending on public availability and provider responses, it can connect an Epic identity to supported gaming platforms.

Treat every link as a sourced observation:

type GamingAccountLink = {
  sourcePlatform: "epic";
  targetPlatform: string;
  targetIdentifier: string;
  collectedAt: string;
  sourceUrl?: string;
};

Do not merge two profiles simply because their display names are similar. Look for multiple consistent signals such as stable platform IDs, the same avatar, matching linked accounts, and compatible activity.

Other Epic Games routes

Osintly exposes focused operations so you can pay only for the data your workflow needs:

Search and suggestions are marked free, which means they do not consume a core-search credit. A paid API plan with the Tools feature is still required. You can verify costs programmatically through the tool cost endpoint described in the Tools API introduction.

Use the all-in-one route carefully

The /all route is convenient when an analyst needs a broad snapshot. It costs two credits and can replace several separate calls. For high-volume products, focused routes may still be more efficient because they reduce payload size and unnecessary collection.

If you set save: true, the Tools API can persist the result and return a result ID. Retrieve it later through the results endpoint documented in the Tools API introduction. This is useful for background jobs and audit trails.

Build a resilient integration

External gaming services can return partial data. Your client should expect missing sections, provider timeouts, and identifiers that resolve differently across regions.

A robust pipeline should:

For quick experimentation, use the hosted Epic Games demo. For production, read the Epic Games API reference, the Tools API overview, and the current API pricing.

From one gaming handle to a wider investigation

Epic Games can be the first step in a broader gaming identity workflow. Once you have a credible linked account, continue with the dedicated Xbox tool, Steam tool, PlayStation tool, or Roblox tool.

Osintly puts those tools behind one authenticated API, with transparent per-route costs and hosted demos for manual validation. Start with an identifier you are authorized to investigate, confirm the result in the Epic Games tool, then automate only the pivots your application needs.