Server population
The region's recorded cluster population over the requested range, with each cluster's own peak and mean, the region's records, and the average population per weekday and hour (UTC) over the trailing four weeks. Wargaming publishes population as an instant and keeps no history, so this series only goes back to when the sampling started. Cached for 60s server-side. Dates are ISO 8601 strings.
Path Parameters
Game server region.
Value in
- "eu"
- "na"
- "asia"
Query Parameters
How far back the population series reads.
"day"Value in
- "day"
- "week"
- "month"
- "year"
Response Body
application/json
curl -X GET "https://example.com/eu/server/stats"{ "region": "eu", "range": "day", "servers": [ "string" ], "points": [ { "at": "2019-08-24T14:15:22Z", "total": 0, "values": [ 0 ] } ], "clusters": [ { "server": "string", "current": 0, "peak": 0, "peakAt": "2019-08-24T14:15:22Z", "average": 0, "share": 0 } ], "current": 0, "average": 0, "peak": { "players": 0, "at": "2019-08-24T14:15:22Z" }, "trough": { "players": 0, "at": "2019-08-24T14:15:22Z" }, "allTimePeak": { "players": 0, "at": "2019-08-24T14:15:22Z" }, "rhythm": [ { "weekday": 0, "hour": 0, "average": 0, "samples": 0 } ], "since": "2019-08-24T14:15:22Z", "until": "2019-08-24T14:15:22Z"}Twitch chat badges GET
Every badge a chat message in this Twitch channel can carry, with its images: Twitch's global badges, with the channel's own subscriber and bits images in place of the global ones they replace. A chat client receives only `set/version` pairs with each message (the IRC `badges` tag), which this resolves. 404 when the login is not a Twitch channel. Cached one hour.
Compare regions GET
Every region's total population on one timeline, for the requested range. Region-less by nature: comparing EU, NA and Asia is the point, and asking one region for the other two would be a strange shape. Cached for 60s server-side. Dates are ISO 8601 strings.