How it works

Every minute, the game's leaderboards are updated. I monitor these changes over time and save diffs for the top 1000 players.
Currently, there's no way to access historical data directly from the game itself - so this is the only way to track it.

Caveats

• Not an actual battle history. Since several battles can complete in the same window of 60 seconds, it's not always possible to attribute every battle and rank change to a specific tank.
• Restricted to ranked top 1000 only. The whole thing works off leaderboard changes, so there's no way to track unranked battles without player authentication.
• Per-battle loadout tracking is too expensive to run against the Tyr API - this would mean hundreds of API calls every minute. Instead, I collect loadouts on a schedule (currently 3-4 times a day), to minimize API load.
• History prior to this project's launch is not available.
• Gaps in Tyr API (or my own backend/networking) availability will result in permanent data loss over that period.
• If Tyr changes or removes the endpoints used, this project may break until manually updated, or get canceled entirely.

API usage

Tyr does not yet provide any official open API or developer program, so I did my best to minimize the number of API calls. Job/request tracking are available on the Status page. Requests are also signed with a custom UA and headers to help identify and manage traffic.

For dear Stoke developers: reach out to me if you are unhappy with the current API usage or have suggestions for improvement.