How to Get Case Hardened Tier Price History

cs2.sh provides Case Hardened quote history for supported Tier 1 through Tier 4 and Blue Gem variants through per-source OHLC and dedicated BUFF tier-and-float buckets.

These series describe active asks, bids, and order counts. CSFloat's completed-sale archive can contain a base Case Hardened aggregate, but it does not collect separate tier or Blue Gem sale histories.

Two tier-level history models#

Per-source tier OHLC#

POST /v1/prices/history can return variant ask and available bid OHLC from December 24, 2025 at 5m, 30m, 1h, or 1d. Variants use stable codes t1, t2, t3, t4, and singleblue. Each source appears only when it has data for that tier and bucket; do not assume the base item's source coverage also exists for every tier.

BUFF tier and float history#

POST /v1/market/buff/history records BUFF range buckets from May 19, 2026. Each Case Hardened tier has its own base bucket and can have float buckets. Ask, average ask, and bid receive OHLC; listing and buy-order volumes are last-observed. Data refreshes every 10 minutes.

Keep CSFloat base sales separate#

POST /v1/archive/csfloat returns daily average completed-sale price and sale count from 2022 for base items with archive data. Its variant collector covers Doppler and Gamma Doppler phases, not Case Hardened tiers. A returned base Case Hardened data[] series therefore cannot be assigned to t1, t2, t3, t4, or singleblue.

Compare a tier with the parent market#

Request the base Case Hardened market_hash_name, then select the desired variant by version. To measure a tier premium from listing OHLC, pair the tier's close_ask with the base item's close_ask at the same bucket.

For a float-specific tier premium, use the dedicated BUFF endpoint and compare the tier's float bucket with both the tier base and parent base buckets. The tier-and-float history guide explains those two benchmarks.

Use a CSFloat base archive only as a separately labeled parent-market reference. It does not validate whether a specific tier cleared near its listing floor.

Applicable endpoints#

History boundaries#

• singleblue is separate from Tier 1. Missing Blue Gem rows should remain missing instead of inheriting Tier 1 data.
• BUFF avg_ask is the average active listing ask. A CSFloat base archive price is the arithmetic average of base-item sales for the UTC day.
• Case Hardened tier sales are not collected as CSFloat archive variants. Missing tier rows must not inherit the base sale aggregate.
• Tier histories group multiple seeds. Pattern placement and exact seed still require item-specific evidence outside these aggregate variant series.
• Requests before each endpoint's start date cannot reconstruct the missing variant history. Keep the boundary visible in charts and comparisons.