Rust player data
Rust player stats API: kills, resources, hours and achievements
Read Steam-published lifetime Rust counters for a public account with one WOK key. The summary names the most requested kills and resources while preserving every numeric counter returned by Steam.
Updated September 26, 2026
WOK APIcurl --fail-with-body --max-time 35 --get \
-H "Authorization: Bearer $WOK_API_KEY" \
--data-urlencode "steam_id=$STEAM_ID" \
"https://woksteamapi.com/v1/rust/summary"Choose the Rust data you need
Set WOK_API_KEY and a 17-digit STEAM_ID on your server. WOK fixes the Rust AppID to 252490; no Valve key or game parameter is required.
| Endpoint | Response | Use it for |
|---|---|---|
GET /v1/rust/summary | kills, resources, combat, stats_by_name | Named lifetime player, scientist, animal kills and resource counters. |
GET /v1/rust/stats | playerstats.stats[] | Raw Steam counter names and values, including counters not mapped in the summary. |
GET /v1/rust/achievements | playerstats.achievements[] | Each published achievement's identifier and numeric achieved flag. |
GET /v1/rust/playtime | response.games[] | Visible Rust lifetime and recent playtime in Steam minutes and decimal hours. |
GET /v1/steam-level | steam_level | Steam account level; this value is independent of Rust. |
Each data request consumes one WOK quota unit. The API reference and OpenAPI schema provide the full request contracts. Read GET /v1/key for your current quota without spending a data request.
Which kills and resources are available?
The table shows exact Steam counter names mapped by /v1/rust/summary. WOK leaves a mapped field null when Steam did not publish that counter for the account.
| WOK field | Steam stat name | Meaning |
|---|---|---|
kills.players | kill_player | Player kills in the Steam lifetime stat. |
kills.scientists | kill_scientist | Scientist NPC kills published by Rust. |
kills.bears / boars / stags / chickens / wolves | kill_bear / kill_boar / kill_stag / kill_chicken / kill_wolf | Separate animal counters. |
resources.wood / stones | harvested_wood / harvested_stones | Published harvesting counters. |
resources.cloth / leather | harvested_cloth / harvested_leather | Published harvesting counters. |
resources.lowgrade_fuel / metal_ore / scrap | acquired_lowgradefuel / acquired_metal.ore / acquired_scrap | Published acquisition counters; they do not establish a particular server or wipe. |
combat.deaths / headshots | deaths / headshot | Published combat counters. |
Example JSON below illustrates the response shape and uses made-up values. Real responses can contain additional keys in stats_by_name; read that object when you need every numeric stat Steam supplied.
WOK API{
"steam_id": "76561198000000001",
"appid": 252490,
"scope": "steam_account_lifetime",
"kills": {
"players": 125,
"scientists": 38,
"bears": 4
},
"resources": {
"wood": 5070,
"stones": 3120,
"metal_ore": 970,
"scrap": 220
},
"combat": {
"deaths": 61,
"headshots": 48
},
"stats_by_name": {
"kill_player": 125,
"harvested_wood": 5070,
"acquired_metal.ore": 970
}
}Hours and achievement flags
Steam returns playtime_forever and sometimes playtime_2weeks in minutes. WOK adds playtime_hours and playtime_2weeks_hours to the same game row; a missing recent value becomes null. An empty response.games can mean Rust is not visible or not owned.
WOK APIcurl --fail-with-body --max-time 35 --get \
-H "Authorization: Bearer $WOK_API_KEY" \
--data-urlencode "steam_id=$STEAM_ID" \
"https://woksteamapi.com/v1/rust/achievements"In playerstats.achievements[], achieved: 1 means unlocked and achieved: 0 means locked. Steam uses apiname for the achievement identifier; WOK also supplies the same value as name. Optional unlocktime is only present when Steam provides it.
Valve's user stats API documents game stats and achievements; Valve's player service API documents owned games, playtime and Steam level.
Scope, privacy and errors
These are lifetime Steam account values across Rust. Steam's public Web API does not attach a Rust server identifier, wipe date or per-server resource ledger to these counters.
For private or unavailable game statistics, WOK returns HTTP 403 with rust_data_unavailable. Keep the value unknown; do not present it as zero or retry it in a loop.
For a temporary Steam failure, WOK returns HTTP 502. Retry after a delay with a cap. HTTP 400 means the SteamID64 input needs fixing; 401, 402 and 429 relate to your WOK key or quota.
Per-server kills, farming, bot kills beyond the published counter, sulfur totals or wipe-specific results require data from that Rust server's own API, plugins or logs. A public Steam profile alone cannot reconstruct them.
Complete Rust API mapRust inventory and valuesSteam profile and name historyAll developer guidesPlan limits