CSFloat Price API for Counter-Strike 2

Fetch live CSFloat listing prices in USD via GET /v1/prices/latest?markets=csfloat — with phase on every row, listing counts, and change metrics. Compare CSFloat vs YouPin in one POST for Western↔CN arbitrage.

What CSPriceAPI provides for CSFloat

Quick start

Full CSFloat snapshot:

curl -s "https://api.cspriceapi.com/v1/prices/latest?markets=csfloat" \
  -H "x-api-key: YOUR_API_KEY"

Batch lookup with CN markets (arb pattern):

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": [
      "★ Butterfly Knife | Doppler (Factory New) (Ruby)",
      "AK-47 | Redline (Field-Tested)"
    ],
    "markets": ["csfloat", "youpin", "buff163", "skinport"]
  }'

Response shape

Excerpt of the OpenAPI example (prices are decimal strings):

{
  "items": {
    "AK-47 | Redline (Field-Tested)": {
      "market_hash_name": "AK-47 | Redline (Field-Tested)",
      "csfloat": {
        "id": 501,
        "market_hash_name": "AK-47 | Redline (Field-Tested)",
        "stattrak": 0,
        "souvenir": 0,
        "exterior": "Field-Tested",
        "price": "18.75",
        "change_24h": "0.20",
        "change_7d": "0.90",
        "change_30d": "-1.10",
        "change_90d": "3.40",
        "avg_7d": "18.60",
        "avg_30d": "19.00",
        "avg_90d": "18.10",
        "count": 320,
        "updated_at": "2026-04-21T12:18:00.000Z",
        "item_page_url": "https://csfloat.com/item/123456789",
        "buff_template_id": 35247,
        "liquidity": "9.10"
      }
    }
  },
  "markets": ["csfloat"],
  "requestor": "customer@example.com",
  "plan": "pro",
  "timestamp": "2026-08-27T14:50:00.000Z"
}

Critical: Each Doppler phase is its own entry: the phase is appended to market_hash_name after the exterior (e.g. ★ Butterfly Knife | Doppler (Factory New) (Ruby)) and the row carries a phase field. Joining on the base name without phase collapses a Ruby into a Phase 2 price.

Reading CSFloat data correctly

Listing price ≠ buy order. CSFloat displays both asks and bids on-site. CSPriceAPI listing endpoints return lowest ask snapshots. CSPriceAPI has no CSFloat buy orders; for bid-side context use the YouPin full buyorder book.

count = listings, not sales. Twelve listings means twelve sellers at or near that price tier — not twelve sales today.

USD only. Convert to CNY/EUR in your layer for cross-market ROI. Do not assume 1:1 with Skinport EUR.

Float premiums. Low-float Factory New listings can carry premiums on CSFloat. For wear-bucket pricing, /v2/prices/float-ranged covers YouPin only.

Cross-market: CSFloat sell vs YouPin buy

Classic Western exit / CN entry check:

1. YouPin ask = cost to buy in China (CNY).
2. CSFloat ask = what Western sellers list at (USD).
3. YouPin buyorder = realistic instant exit in CN (dedicated endpoint).

Net ROI must subtract: CSFloat seller fee (~2%), withdrawal, FX spread, and time risk.

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

Align buyorder rows by (market_hash_name, phase) the same way as listing prices.

Worked example: Phase-aware spread

Item: ★ Karambit | Doppler (Factory New), Ruby

Illustrative prices, scaled to the Ruby/Phase 4 ratio (about 5.6×) for the Karambit FN in the Doppler guide snapshot of 26 Sep 2026 (Ruby ≈ €6,448, Phase 4 ≈ €1,148 median ask).

At ¥7.2/USD, YouPin ≈ $6,944. CSFloat ≈ $6,950 — rough parity on this phase. If you accidentally matched YouPin's Phase 4 row (~$1,240), you'd see a fake ~460% arb.

Always filter: phase == "Ruby".

History

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