Steam Price API for Counter-Strike 2

Pull live Steam Community Market prices for CS2 skins via GET /v1/steam: best ask, best bid, spread and the in-depth order book, with the same API key you use for YouPin, BUFF163 and Skinport. Steam prices are a reference, not withdrawable cash.

What CSPriceAPI provides for Steam

CSPriceAPI is an independent aggregator, not an official Valve API. Steam has no public market API for third-party developers.

Quick start

All items on Steam:

curl -s "https://api.cspriceapi.com/v1/steam" \
  -H "x-api-key: YOUR_API_KEY"

The same skins on YouPin and BUFF163 for comparison (max 100 per POST; Steam is not part of /v1/prices/latest):

curl -s -X POST "https://api.cspriceapi.com/v1/prices/latest" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":["AK-47 | Redline (Field-Tested)"],"markets":["youpin","buff163"]}'

Single lookup:

curl -s "https://api.cspriceapi.com/v1/steam?market_hash_name=AK-47%20%7C%20Redline%20(Field-Tested)" \
  -H "x-api-key: YOUR_API_KEY"

Response fields (typical row)

Excerpt of the openapi.yaml example:

{
  "data": [
    {
      "market_hash_name": "AK-47 | Redline (Field-Tested)",
      "currency": "USD",
      "best_ask": "12.45",
      "ask_listings": 85,
      "best_bid": "11.90",
      "bid_orders": 240,
      "spread": "0.55",
      "spread_pct": "4.42",
      "liquidity": "8.40",
      "updated_at": "2026-08-28T10:00:30.000Z",
      "orderbook": {
        "asks": [{ "price": "12.45", "quantity": 2 }],
        "bids": [{ "price": "11.90", "quantity": 3 }]
      }
    }
  ]
}

Reading Steam data correctly

Listing ≠ sale. Steam best_ask is what sellers ask right now. A skin can sit listed for weeks without selling. Confirm with market sales search when sizing a trade.

Steam Wallet ≠ cash. Valve takes ~15% on sales and funds stay in Steam Wallet. A $150 Steam listing does not equal $150 bank cash. For cash valuation, weight YouPin898 or BUFF163 (CNY) and Western markets (EUR/USD).

Steam is slow to react. Skinport and YouPin often move first on meta shifts (tournament stickers, case drops). Steam lags — good for reference, risky as sole arb target.

Null is missing, not zero. If an item returns no row, it may have zero listings — do not substitute 0 in portfolio math.

Cross-market context (why traders still pull Steam)

International traders use this pattern daily:

1. YouPin898 sets the global wholesale reference (CNY).
2. BUFF163 tracks YouPin closely — gaps = CN arbitrage.
3. Skinport / CSFloat = Western cash venues (EUR/USD).
4. Steam = visibility and wallet-only liquidity.

Compare them with two calls: GET /v1/steam for Steam and one /v1/prices/latest request for the other three.

curl -s -X POST "https://api.cspriceapi.com/v1/prices/latest" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":["★ Karambit | Doppler (Factory New) (Ruby)"],"markets":["youpin","buff163","skinport","csfloat"]}'

Match rows by (market_hash_name, phase). A Karambit Doppler Ruby on CSFloat is not comparable to Phase 4 on Steam.

Worked example: Steam premium vs YouPin reference

Suppose the two calls return:

At ¥7.2 / USD, YouPin ≈ $389 cash-equivalent listing. Steam shows ~34% above the CN reference — common on liquid skins (Steam convenience premium). That gap is not free profit: you cannot withdraw Steam Wallet to bank at par.

Decision: A bot should not auto-buy on Skinport because Steam is higher unless it models wallet value separately.

History & sales

Steam is not covered by the price-history or sales endpoints. For long-range trends, use daily history (1 year+, Enterprise) from a history market such as YouPin:

curl -s "https://api.cspriceapi.com/v1/prices/youpin/history?market_hash_name=AK-47%20%7C%20Redline%20(Field-Tested)" \
  -H "x-api-key: YOUR_API_KEY"

Completed sales are available for YouPin, CSFloat and Skinport (the last 72 hours through the API (older sales as an archive on request), Enterprise):

curl -s "https://api.cspriceapi.com/v1/market-sales/search?market_hash_name=AK-47%20%7C%20Redline%20(Field-Tested)" \
  -H "x-api-key: YOUR_API_KEY"