Tank changes feed
The global tank-rebalance feed for a region: recent characteristic changes across every tank, grouped by game version (newest first) and then by tank (heaviest-hit first). Firepower, gun handling, mobility, survivability and concealment buffs and nerfs, as Wargaming ships them. Identity comes from the region's own catalogue, so a tank absent from a server is left out of that server's feed. Values are raw stored values; apply each field's scale to display.
Path Parameters
Game server region.
Value in
- "eu"
- "na"
- "asia"
Response Body
application/json
curl -X GET "https://example.com/eu/tanks/changes"{ "versions": [ { "gameVersion": "string", "capturedAt": "2019-08-24T14:15:22Z", "tanks": [ { "identity": { "tankId": 0, "slug": "string", "tier": 0, "type": "string", "nation": "string", "name": "string", "shortName": "string", "tag": "string", "isPremium": true, "isReward": true, "isCommonTest": true, "isHidden": true, "variant": "string", "testChanges": 0, "role": "string", "contourIcon": "string", "bigIcon": "string" }, "changes": [ { "field": "string", "previous": 0, "next": 0 } ] } ] } ]}Tanks performance GET
Server-wide performance for every tank on a region, averaged over tracked players: win rate, average damage, WN7/WN8/WNX, kills-per-death, assistance, spots, hit and penetration rate, blocked damage and survival, plus Marks of Excellence / Mastery holder counts. One row per vehicle in the region's catalogue; `stats` is null until the by-tank cron has coverage.
Compare tanks GET
Everything a side-by-side comparison of 2 to 4 columns renders (`?slugs=is-7,e-100`): each vehicle's specifications, module combinations, equipment slots, crew and progression, plus its server-average performance. The mountable catalogues (equipment, directives, consumables, crew skills) are hoisted out of the vehicles and described once under `catalog`, referenced by key, and `ranges` carries the catalogue-wide spread of every characteristic so a client can score a vehicle per category. A slug may suffix the game client to read the vehicle on (`?slugs=amx-13-90,amx-13-90@ct`), which is how a vehicle is compared against what the running Common Test makes of it, and every column carries back the `client` it was read on. It may also suffix a position (`?slugs=is-7,is-7~2`), which is how the same vehicle is compared under two setups: both columns carry the vehicle's data, told apart by `occurrence`. A repeat spelled the same way twice still collapses, and a slug the catalogue doesn't know is dropped rather than failing the request, as long as two columns remain.