# cs2.sh vs Official CSFloat API for CS2 Market Data

> Use [CSFloat's official API](https://docs.csfloat.com/#introduction) when you need individual active listings, asset-level float, paint, sticker, seller, or auction fields, or the ability to list an item. Use cs2.sh when you need the lowest sell listing, highest buy order, intraday history, daily completed-sale price and volume from 2022, variant history, or liquidity across the full item schema.

## CSFloat's API is a listing interface

The [official CSFloat documentation](https://docs.csfloat.com/#introduction) publishes a collection endpoint for active listings, a lookup for one listing, and an authenticated operation to list an item. The collection endpoint supports filters for `market_hash_name`, float, paint index, paint seed, price, rarity, collection, stickers, seller, and listing type. Results are cursor-paginated with at most 50 listings per response.

That raw listing detail is more useful than an item-level minimum when the product is a listing browser, sniper, or seller tool. It is not the same product as a historical market database. The public documentation does not publish price history, completed-sale history, liquidity, or a public buy-order endpoint.

## Current differences

| Requirement | [CSFloat API](https://docs.csfloat.com/#introduction) | cs2.sh |
| --- | --- | --- |
| Individual listings | Rich asset, seller, price, and auction records | Item-level current data on public plans; live full-depth CSFloat listings are an Enterprise option |
| Current item price | Compute it by paging and filtering listings | Ready-to-use `ask` for the lowest sell listing and `bid` for the highest buy order |
| Buy-order prices | No endpoint in the published docs | Current CSFloat bid on most items, including many Doppler variants |
| Intraday history | No published endpoint | Ask and bid OHLC at `5m`, `30m`, `1h`, and `1d` |
| Completed sales | No published endpoint | Daily average completed-sale price and completed-sale volume from 2022 onward |
| Variants | Filter listing assets by paint fields | Doppler, Gamma Doppler, and Case Hardened in a stable `variants` object, including historical queries |
| Liquidity | No published endpoint | Daily liquidity bucket and estimated sale time for every item and variant |
| Throughput terms | Maximum 50 listings per page; the docs show 429 errors but do not publish a numeric request allowance | Unlimited monthly requests at 10 requests per second |

For cs2.sh, `ask` means the lowest sell listing and `bid` means the highest buy order. Those item-level values are intentionally different from a raw list of uniquely painted and stickered assets.

## Use CSFloat for exact listings and selling

[CSFloat's official API](https://docs.csfloat.com/#introduction) is the right source when an application needs to show or act on a particular CSFloat listing. It provides the asset's float, paint seed, stickers, auction state, seller, and listing ID, and it supports creating a listing. Those listing-level records are intentionally outside the public cs2.sh item-level response; cs2.sh offers a live CSFloat listing feed only on Enterprise.

## Add cs2.sh for completed sales and market history

cs2.sh provides the market-level record around those assets: current bid and ask data, OHLC at four intervals, daily completed-sale price and volume from 2022, per-variant current and historical prices, and liquidity estimates. A listing browser can use CSFloat for the exact asset a buyer sees and cs2.sh for the price, sale, variant, and liquidity history needed to evaluate it.

The roles are complementary rather than interchangeable: CSFloat is the listing and marketplace-action API; cs2.sh is the retained market-data API.

## What cs2.sh returns for CSFloat

The CSFloat source arrives alongside five other marketplaces in one response, keyed by the same `market_hash_name`:

```json
"csfloat": {
  "updated_at": "2026-07-26T18:53:05.094Z",
  "collected_at": "2026-07-26T18:53:05.134Z",
  "ask": 107.99,
  "ask_volume": 227,
  "bid": 105
}
```

CSFloat publishes no buy-order count, so `bid_volume` is absent here exactly as it is at source. For completed sales, `POST /v1/archive/csfloat` returns a daily row per item from 2022:

```json
"data": [
  { "date": "2026-04-27", "price": 149.76, "volume": 8 }
]
```

`price` is the arithmetic average of every CSFloat sale that day and `volume` is the sale count. Doppler, Gamma Doppler, and Case Hardened variants carry their own series under `variants`, each with an independent daily average, so a Ruby is priced separately from its base item rather than blended into it.

| Property | Value |
| --- | --- |
| Sale coverage | Daily from 2022 |
| Listing history | Ask and bid OHLC from December 24, 2025 |
| Items per request | 100 |
| Refresh | Prices ~5 min; CSFloat variants ~10-15 min; sale archive ~1-2x per day |
| Access | Current prices on all plans; history and archive need Scale or Enterprise |

Disclosure: this comparison is published by cs2.sh. CSFloat endpoints, filters, pagination, and published limits were checked against its official documentation on August 5, 2026.