Replay Parser

Overview

The Replay Parser reads binary .replay files and returns structured JSON. There are two ways to use it:

• Upload: You supply a .replay file as multipart/form-data. Useful when you have files locally or from your own capture pipeline.
• Fetch-and-Parse:You supply a tournament match ID. We call Epic's datastorage API, download the replay, parse it, and return the result. No file handling on your end.

All requests require an x-api-key header with a valid API key.

Credit System

Parsing operations consume daily credits from your plan quota. Credits reset at midnight UTC.

Upload endpoint costs

Fetch-and-parse endpoint costs

Server vs Client Replays

This is the most important distinction to understand before building with the parser.

Client replays

Recorded locally by a player's game client. Saved to %LOCALAPPDATA%\FortniteGame\Saved\Demos\on Windows. Contains the recording player's own summary statistics written at match end, plus cosmetic data.

Server replays

Recorded by the game server. Epic stores them centrally for tournament and competitive events. Contains replicated state for all players— not just one player's perspective. No per-client stats like accuracy or materials, but full per-player damage/kills/reboots. The isServerReplay field is true and root-level stats is null.

How to Obtain Replays

Client replays

Fortnite saves replays automatically. Users can also download them from the in-game Replays menu. For replays stored server-side by Epic, use the Replay Service API (requires OAuth token).

Tournament / server replays

Use the Fetch-and-Parse endpoints— just provide the match ID and we handle the rest. To find match IDs, call Epic's tournament sessions endpoint:

GET https://fngw-mcp-gc-livefn.ol.epicgames.com/fortnite/api/game/v2/events/v2/sessions/{eventId}/{windowId}
  ?page=0&rank=0&teamAccountIds={accountId}

Each session entry contains a "replayId" field.

See EPIC_ENDPOINTS.md for the full list of tournament endpoints and auth requirements. Once you have a match ID, pass it directly to /api/v1/replays/{matchId}/parse/broadcast.

Upload Endpoints

All upload endpoints accept multipart/form-data with the file under the key file.

{
  "name": "FNGameUSW_00-...",
  "replayId": "...",
  "version": "++Fortnite+Release-34.00",
  "isServerReplay": false,
  "stats": {
    "eliminations": 3, "damage": 412, "accuracy": 0.28,
    "placement": 4, "assist": 1, "damageTaken": 200,
    "damageStructures": 50, "matsFarm": 300, "matsUsed": 150,
    "totalPlayers": 100
  }
}

Fetch-and-Parse Endpoints

Pass a tournament match ID — we call Epic's datastorage API, download the replay chunks, assemble the binary, and parse it. Same response shapes as the upload endpoints. Match IDs come from Epic's tournament events API.

curl -H "x-api-key: YOUR_KEY" \
  "https://prod.api-fortnite.com/api/v1/replays/FNCOMP-USW1-FNCS-GAME1/parse/broadcast"

Data Availability Matrix

✓ = always present  ·  S = server replays only  ·  C = client replays only  ·  — = not included

Response Shape Reference

Coordinate System

All x / y values use Unreal Engine world coordinates (Unreal Units). The map is centered at (0, 0). Coordinates range roughly from -131072 to 131072on both axes depending on the season's map bounds.

The worldBounds object in /parsing/map gives the exact bounds for the specific match. To normalize to 0–1 for overlay rendering:

normalizedX = (x - worldBounds.minX) / (worldBounds.maxX - worldBounds.minX)
normalizedY = (y - worldBounds.minY) / (worldBounds.maxY - worldBounds.minY)