How to Get Fade Float and Percentage Price History

cs2.sh exposes BUFF float_fade buckets that price an exact float range and Fade percentage range together, with OHLC history from May 19, 2026.

Float and Fade premiums overlap. Adding a float-only premium to a Fade-only premium double-counts listings that can belong to both groups. The combined bucket is the direct market slice for both attributes.

BUFF range combinations#

GET /v1/market/buff/latest splits a Fade item into available base, float, fade, and float_fade buckets.

Each range uses an inclusive min and exclusive max. bucket_id stays stable between latest and history. Current buckets contain ask, avg_ask, bid, ask_volume, and bid_volume and refresh every 10 minutes.

Select and compare history#

Fetch the latest BUFF snapshot and choose the single float_fade bucket whose float and Fade bounds contain the item attributes. Retain its matching base, float, and fade buckets when available.

Request the same market_hash_name on POST /v1/market/buff/history and join series by bucket_id. Compare closing asks at shared timestamps. The combined-to-float comparison isolates the observed Fade difference within a similar float range; combined-to-fade isolates the float difference within a similar Fade range.

History provides ask, average-ask, and bid OHLC at 30m, 1h, or 1d. It starts May 19, 2026 and requires Scale or Enterprise access.

Applicable endpoints#

What changes the comparison#

• Not every item has every one-dimensional or combined bucket. Missing slices must remain unavailable.
• Discover ranges from the response. Common float bands are not a contract for every item.
• A bucket close_ask is the last listing floor, not a completed sale or an exact appraisal.
• Thin ask_volume allows one listing to move the floor substantially.
• Compare only shared timestamps. Forward-filling one side can create a premium that was never observed concurrently.

The BUFF history reference documents the OHLC point fields.