Use the same normalized response model as the other supported economies while keeping Rust's real Steam pagination intact.
Designed for backend workflows
Resolve a SteamID or community profile, request game=rust, and continue with the exact returned cursor. ItemData coordinates public refreshes and exposes the result source in response headers.
One normalized JSON response model across supported Steam economies.
Durable public page snapshots with observable HIT, MISS, STALE, and BYPASS behavior.
Cursor pagination that preserves Steam's real page boundaries.
Bearer API-key authentication, explicit timeouts, and stable error codes.
Optional authorized access for inventories that need a Steam session.
Private access remains caller-authorized
When a user explicitly supplies their Steam session, ItemData derives the owner from that credential, bypasses shared inventory storage, and never persists the session value.
NEXT STEP
Fetch a Rust inventory page.
Use the documented game value and keep every credential server-side.