Tanks

Tank detail

Everything the tank page renders in one payload: identity, top players per rating metric (WN7/WN8/WNX), server-average performance, WN8/WNX expected values, combat specifications, current Marks of Excellence/Mastery with their daily history, and the cheapest research path. slug in the response is the canonical slug; callers that reached the tank through a legacy numeric id should redirect to it. Dates are ISO 8601 strings.

get/{region}/tanks/{slug}/detail

Request

  • Base URL: https://unicum.gg/api
  • URL: https://unicum.gg/api/{region}/tanks/{slug}/detail
  • Auth: none required

Path parameters

region'eu' | 'na' | 'asia' required

Game server region.

slugstring required

Tank slug (e.g. is-7).

Query parameters

client'live' | 'ct'

Which game client to read the vehicle's characteristics from. ct serves what the running Common Test build makes of it, so a tank can be inspected and configured the way the next update would ship it. Falls back to live when no test is running or when it leaves this vehicle alone.

Response

Successful response

tankIdnumber required
slugstring required

Canonical slug. Callers that reached the tank through a legacy id or wrong-case slug should redirect to it.

specsstring nullable required
skillTreeTankSkillTree required(unresolved $ref)
mechanicstring nullable required

Which mechanic the vehicle's second state is, where it has one: siege, wheeled, dualGun, twinGun, turboshaftEngine, shellParamsSwitcher or lowChargeShot. The client tags all of them the same way, so this is what tells them apart. Null for the vast majority of vehicles, which have no second state.

paintLock'locked' | 'factory' required

Why the game refuses to let a vehicle be dressed: locked for one whose customization is off entirely (a mode-locked machine, or a reward vehicle that is itself a style), factory for one wearing a livery of its own that cannot come off (the Skorpion G, the Tiger 131). The customization filters carry none of this, so a wardrobe built from them alone offers paint on every one of them.

hasHistoryboolean required

Whether the tank has anything on its History tab: a recorded characteristic change, or a known lifecycle event (release / dev). Drives the History tab's visibility.

client'live' | 'ct' required

Which game client these characteristics were read from. Only the vehicle's own data follows it: server stats, marks and best players always come from the region's live client, since a test server has no players to measure.

testVersionstring nullable required

The Common Test build that rebalances this tank, e.g. 2.4.0.5415. Null when no test is running or when this one leaves the vehicle alone. Present whichever client the payload is for, so a caller can offer the other one.

Changes

No recorded changes to this operation across all 1 revision of this API.