THE FINALS API

Getting started

Everything this site shows publicly is available as JSON. There is no API key and no sign-up for any of it. Every endpoint is a GET, CORS is open to all origins, so you can call it straight from a browser, a bot, a spreadsheet or a script.

One exception: the ownership endpoints, which resolve an Embark account to the Discord user who owns it, need a key we issue by hand. Everything else is open.

Base URL   https://api.finalstracker.net/v1

curl "https://api.finalstracker.net/v1/leaderboard?limit=5"
curl "https://api.finalstracker.net/v1/players/Balise-2431"

Identifying a player. An Embark ID looks like Balise#2431. A # cannot survive a URL round trip (it is a fragment delimiter, and tools that decode it drop everything after it), so in a path the # becomes a -: Balise-2431. Percent-encoded Balise%232431 also works, but the dashed form is the one that survives being pasted into things.

Every response carries a meta block saying which board it came from. Data refreshes on a roughly 10 minute snapshot cycle, and responses are cached for up to 60 seconds, so generatedAt is when the body was built and snapshotAt is when the underlying board was read. Polling faster than the snapshot interval returns the same numbers.

"meta": {
  "season": "s11",
  "snapshotId": 7649,
  "snapshotAt": "2026-08-15T02:20:12.792Z",
  "boardSize": 10000,
  "generatedAt": "2026-08-15T02:31:04.118Z"
}

Versioning. The version lives in the path. Fields are only ever added within v1; a field that ships here keeps its name and its meaning. Anything that would break an existing integration goes in a v2 instead. Write your client to ignore fields it does not recognise.

Errors are JSON with an HTTP status: 400 a bad parameter, 404 no such player or endpoint, 429 rate limited, 503 a snapshot is being written, retry shortly. The body is { "error": "not_found", "message": "…", "docs": "…" }.

Rate limits and fair use

300 requests per minute per IP. A few endpoints that run uncached text searches are tighter: the leaderboard is 240/min, player history 120/min, and /search 60/min. Exceeding a limit returns 429 with a Retry-After header. There is no daily cap.

This runs on one small server that also serves the website, so please be a considerate neighbour: cache what you fetch, page through the board rather than hammering it, and do not poll faster than the ~10 minute snapshot cycle, since you will only get the same numbers back. If you are building something that needs more, email us and we will work it out rather than rate limiting you into a corner.

Status and leaderboard

{
  "total": 10000, "limit": 2, "offset": 0, "include": "board", "sort": "rank",
  "players": [
    {
      "rank": 1,
      "embarkId": "Balise#2431", "name": "Balise", "tag": "2431",
      "league": "Ruby",
      "rankScore": 71422,
      "change24h": { "rank": 0, "rankScore": 412 },
      "changeSinceLastSnapshot": 0,
      "platforms": { "steam": "Balise", "psn": "TTV-Balise", "xbox": null },
      "club": "BERGR",
      "activity": "active",
      "offBoard": false, "estimated": false, "lastKnown": null,
      "ownership": { "claimed": false, "verified": false, "discordUserId": null,
                     "embarkUserId": null, "linkedAt": null },
      "profileUrl": "https://finalstracker.net/p/Balise-2431"
    }
  ],
  "meta": { }
}

Players

{
  "player": {
    "embarkId": "PlayrTTV#0245", "name": "PlayrTTV", "tag": "0245",
    "standing": {
      "state": "onBoard", "rank": 764, "rankScore": 45569, "league": "Diamond 2",
      "change24h": { "rank": -34, "rankScore": -136 },
      "activity": null,
      "platforms": { "steam": "Playr", "psn": null, "xbox": null },
      "club": "BUNNX"
    },
    "season": {
      "id": "s11", "peakRank": 88,
      "record": {
        "wins": 21, "losses": 8, "moves": 29, "netRankScore": 4510,
        "winRate": 0.7241, "winRateSampleFloor": 20,
        "streaks": { "currentWin": 0, "currentLoss": 2, "bestWin": 6, "worstLoss": 3 },
        "firstSeenAt": "2026-06-22T13:13:57.069Z",
        "lastActiveAt": "2026-08-14T22:50:12.327Z",
        "adjustmentThresholdRs": 3500
      }
    },
    "career": {
      "seasons": [ { "season": "s9", "rank": 7654, "basis": "final" } ],
      "seasonsPlayed": 6, "bestRank": 88
    },
    "seasonRecords": [ ], "placements": [ ],
    "names": { "former": [ ], "renamedTo": null },
    "badges": [ { "slug": "og", "title": "OG", "rarity": "legendary" } ],
    "ownership": { "claimed": true, "verified": true,
                   "linkedAt": "2026-08-14T23:00:13.151Z",
                   "discordUserId": "restricted", "embarkUserId": "restricted" }
  },
  "meta": { }
}

{
  "embarkId": "Balise#2431", "names": ["Balise#2431"],
  "points": [
    { "at": "2026-06-22T13:13:57.069Z", "rank": 14, "rankScore": 65389,
      "season": "s10", "recordedAs": "Balise#2431", "adjustment": false }
  ],
  "count": 1, "truncated": false, "meta": { }
}

Seasons and cutoffs

Adjustments, renames and disappearances

Tournaments and badges

Ownership key required

Players can link their Embark ID to their Discord account on finalstracker.net, proving ownership either through our browser extension (which reads the ID from Embark itself) or an in-game code challenge (which we read back off the public leaderboard). Both are verified at a source the claimant does not control.

Whether an account is verified is public. Who verified it is not. Every player object carries an ownership block saying whether the account has been claimed and proved, which is the same thing the checkmark on the leaderboard already says. The owner's Discord user ID is restricted: a Discord ID resolves to a real person, and publishing it beside an in-game identity would let anyone build a complete Discord-to-Embark directory of every player who ever verified, just by paging through the leaderboard. Without a key those two fields read "restricted" rather than a value.

// no key
"ownership": { "claimed": true, "verified": true,
               "linkedAt": "2026-08-14T23:00:13.151Z",
               "discordUserId": "restricted", "embarkUserId": "restricted" }

// with an ownership-scoped key
"ownership": { "claimed": true, "verified": true,
               "linkedAt": "2026-08-14T23:00:13.151Z",
               "discordUserId": "743956656429203535", "embarkUserId": null }

Getting a key. Access is granted by hand, to named parties with a reason to resolve claims: tournament organizers checking that a sign-up is really the account it says it is, and community bots assigning verified roles. Email [email protected] with who you are, what you are running and what you need it for. Keys are free, revocable, and tied to you.

Send it as a header. Never in a query string, which would put it in logs and browser history:

curl -H "Authorization: Bearer ftk_your_key_here" \
  "https://api.finalstracker.net/v1/ownership/embark/PlayrTTV-0245"

Treat it as a secret: server side only, never shipped in a web page or a public repo. 401 key_required means no key was seen, 403 insufficient_scope means the key is valid but not for this. GET /v1 echoes your key's label and scopes back, which is the quickest way to confirm it is arriving.

verified is the field that matters. true means the claim was proved at the source, by one of the two methods above. false means it is one of a handful of links made before August 2026 under an older, optimistic method that took the claimant's word for it. Both show a checkmark on the site; only this field tells them apart. If you are granting anything on the strength of a claim, require verified: true.

Linking is optional for players, and unlinking on the account page removes them from these responses immediately. See the Privacy Policy.

{
  "embarkId": "PlayrTTV#0245",
  "claimed": true,
  "verified": true,
  "linkedAt": "2026-08-14T23:00:13.151Z",
  "discordUserId": "743956656429203535",
  "embarkUserId": null,
  "meta": { }
}

Estimated values, and how to not misreport them

Embark publishes only a top 10,000. An account below that line is invisible to everyone, including us. Rather than have players vanish, the leaderboard can be extended past the cutoff with include=tail, and a player profile reports the same thing in standing.estimatedRank.

On those rows, both headline numbers are estimates, and they are flagged estimated: true so you can label them. rank is our ordering of accounts that recently fell off, not a position Embark published. rankScore is the top-10,000 cutoff the account fell under, never a score it actually held. What it really last held is in lastKnown. Presenting an estimated rank score as a player's real rating is the single easiest mistake to make with this API, which is why it has its own section.

Two smaller ones worth knowing: a historic player has placements but no time series, so charts should say so rather than render empty; and tail rows carry no league or platform handles, because we do not retain them for accounts that have left the board.

Terms of use

Free to use, including commercially. In return, two asks and one rule:

• Credit finalstracker.net where the data is shown, with a link if the medium allows one. Some of this (derived records, activity, cutoff history, tournament badges) exists nowhere else and was built here.
• Do not present derived or estimated figures as official. Win/loss, activity, cutoff projections, estimated ranks and ban detections are ours, not Embark's. The relevant sections above say which is which.
• No scraping around the API. If you need bulk data, page through these endpoints. Hammering the website's HTML instead, or trying to route around the rate limit, is the one thing that will get an IP blocked.

The API is offered as-is, with no uptime guarantee. It is a community project, run on one server, and it can go down or change. The site's Terms of Service apply.

This is unofficial and not affiliated with or endorsed by Embark Studios. THE FINALS is a trademark of Embark Studios AB.

Changes and contact

Additions are announced in the Discord. Questions, bug reports, a higher rate limit, or a request for data that is on the site but not yet in the API: [email protected] with API in the subject. If you build something with it, we would genuinely like to see it.