How to Get Steam Orderbook History

Updated

API reference: GET /v1/market/steam/latest · POST /v1/market/steam/history

POST /v1/market/steam/history returns latest-in-bucket full-depth Steam orderbook snapshots from June 9, 2026 at 1h and 1d intervals.

Each point is one complete bid and ask ladder selected as the latest observation inside its bucket. It is not OHLC and does not contain every orderbook change during the interval.

Historical orderbook shape#

Every history point contains bucket, updated_at, collected_at, top, and depth.

top holds best ask, best bid, and total sell-order and buy-order counts. depth holds columnar ask and bid arrays. Ask prices are ascending, bid prices descending, and prices[i] pairs with the exact non-cumulative quantity in volumes[i].

This is the same ladder shape as GET /v1/market/steam/latest, which makes current and historical fill logic consistent.

Query and replay the books#

Send up to 100 exact regular market_hash_name values with a start, exclusive end, and interval. 1h supports up to 90 days; 1d has no public maximum range. Data updates every 10 minutes.

For each point, walk the ask ladder to estimate a historical buy fill or the bid ladder for a sell fill. Compare average fill with the point's top price to measure visible slippage. Use collected_at as the earliest time the selected snapshot was available to downstream logic.

The current orderbook guide explains level pairing and top versus depth counts.

Applicable endpoints#

Endpoint Returns Plans
POST /v1/market/steam/history Historical full-depth snapshots Scale, Enterprise
GET /v1/market/steam/latest Current full-depth snapshot All plans
POST /v1/archive/steam Native completed-sale median and volume Scale, Enterprise

Backtest boundaries#

  • Orderbook history starts June 9, 2026. Earlier requests cannot return depth.
  • A point is latest-in-bucket, not OHLC. It does not show the highest or lowest level seen earlier in that hour.
  • volumes[i] is quantity at one price, not cumulative depth.
  • Regular items only are supported; phase and tier variants are excluded.
  • Visible orders can be canceled, so historical ladder fills are modeled from observed supply and demand, not proof of execution.

The Steam orderbook history reference defines the exact point semantics.