Overview

Zyron Replay Parser API

Turn a raw Fortnite .replay file into clean, structured JSON — the match's eliminations plus the uploader's placement and stats — extracted server-side from the replay's event data.

The Replay Parser accepts an uploaded Unreal Engine .replay file and reads its event chunks to reconstruct what happened in the match. You send one file; you get back an ordered elimination feed, a summary for the player who recorded the replay, and the list of Epic account IDs seen in the match — no game client, no pairing, and no telemetry pipeline required on your side.

Same parser Zyron runs in production

This is the same battle-tested parser Zyron uses to score its own tournaments. It is built for reliability on real, in-the-wild replay files rather than a lab sample set.

What it does

Given a valid .replay upload, the API returns four things:

Match metadata — start time, length, game build, and the replay's internal name.
Reporter summary — the placement, lobby size, and elimination count for the player who recorded the replay.
Elimination feed — every elimination and knock, in time order, with eliminator and eliminated identifiers.
Participants — the distinct Epic account IDs that appear in the elimination feed.

Limitations

The parser is deliberately focused. It reads only the replay's event-chunk data — the eliminations and the uploader summary — and does not decode full match telemetry such as per-tick positions, loadouts, or building. A few things worth knowing:

Player identifiers are lowercase 32-character hexadecimal Epic account IDs, for example a1b2c3d4e5f60718293a4b5c6d7e8f90.
Bot players are flagged with an eliminatorIsBot / eliminatedIsBot boolean, and their account ID is an empty string "".
A small number of elimination events can fail to decode on unusual builds; that count is surfaced as meta.elimParseFailures (usually 0).

Base URL

All endpoints are served under a single versioned base URL:

text

https://api.zyron.pro/api/v1

Next steps

Continue to the pages below to start integrating:

AuthenticationHow to send your API key with every request.Replay Parser referenceThe full endpoint, request format, and response schema.Rate limitsFree and Pro tiers, and the headers on every response.ErrorsThe error shape and every status code you may see.

Need a key?

Keys are issued manually by the Zyron team — there is no self-serve signup. Use the Get an API key button in the top bar, or read the Authentication page.