Get Item Listings

Returns individual listings for a specific item. Use this when you want to let users pick a specific skin variant (different float, stickers, etc.) rather than just the cheapest one. Authentication: Client Token (Authorization header)

Request

GET https://api.assetpay.gg/client/market/item?itemId=0010f8d48278ccb8&delivery=any&page=1
Authorization: CLIENT_TOKEN

Query Parameters

Parameter	Type	Default	Description
`itemId`	string	Required*	Catalog item ID (1-256 chars): the `itemId` of a `/client/market` row, or the `id` of a suggestion. Provide this or `marketHashName`; `itemId` wins when both are sent.
`marketHashName`	string	Required*	Exact market hash name (1-256 chars, e.g. `AK-47 \| Redline (Field-Tested)`), resolved to the catalog item id. Ignored when `itemId` is supplied.
`delivery`	string	`any`	`"any"`, `"standard"` (bot sources from supplier and sends trade offer) or `"instant"` (immediate delivery from pre-positioned stock). Filters listings by delivery mode.
`phase`	string	-	Doppler phase: `"Phase 1"` to `"Phase 4"`, `"Ruby"`, `"Sapphire"`, `"Black Pearl"`, `"Emerald"`. Returns only that phase’s listings. Combinable with `delivery`.
`floatMin`	number	-	Lower bound on the item float/wear value (`0` to `1`).
`floatMax`	number	-	Upper bound on the item float/wear value (`0` to `1`).
`page`	number	`1`	Page number
`perPage`	number	`50`	Listings per page (max 100)

* Provide either itemId or marketHashName.

Response

{
  "requestId": "...",
  "success": true,
  "data": [
    {
      "id": "listing-uuid-1",
      "name": "AK-47 | Redline",
      "marketHashName": "AK-47 | Redline (Field-Tested)",
      "type": "Rifle",
      "iconUrl": "IzMF03bk9WpSBq-S-ekoE33L-iLqGFHVaU25ZzQNQcXdA3g5gMEPvUZZEfSMJ6dESN8p_2SVTY7V2N4MxGVIwXpaL3_a3Hh...",
      "appid": 730,
      "tradable": true,
      "marketPrice": 10.50,
      "offer": {
        "price": 10.50,
        "delivery": "standard"
      },
      "exterior": "Field-Tested",
      "wear": "0.15234",
      "paintSeed": 123,
      "stickers": [
        {
          "name": "iBUYPOWER | Katowice 2014",
          "marketHashName": "Sticker | iBUYPOWER | Katowice 2014",
          "slot": 0,
          "wear": 0,
          "iconUrl": "IzMF03bi9WpSBq-S-ekoE33L-iLqGFHVaU25Zzc..."
        }
      ]
    },
    {
      "id": "listing-uuid-2",
      "name": "AK-47 | Redline",
      "marketHashName": "AK-47 | Redline (Field-Tested)",
      "type": "Rifle",
      "iconUrl": "IzMF03bk9WpSBq-S-ekoE33L-iLqGFHVaU25ZzQNQcXdA3g5gMEPvUZZEfSMJ6dESN8p_2SVTY7V2N4MxGVIwXpaL3_a3Hh...",
      "appid": 730,
      "tradable": true,
      "marketPrice": 9.80,
      "offer": {
        "price": 9.80,
        "delivery": "instant"
      },
      "wear": "0.35678",
      "paintSeed": 456
    }
  ]
}

Each listing represents a specific item instance with its own float value, stickers, and price. Use the id and offer.price when initiating a withdrawal. On supplier listings marketPrice equals offer.price, and type and iconUrl are always present (an empty string when unknown). When pool stock is included (any delivery other than "standard"), pool listings are merged with supplier listings and the combined list is sorted by offer.price ascending before it is paginated. Pool listings carry assetId and botInfo, have no marketPrice, and always deliver "instant". In a merged response only the first min(100, page * perPage) supplier listings are fetched, so supplier listings deeper than that can’t be reached by paging. If supplier listings can’t be loaded, the pool listings are returned without an error.

This endpoint is currently CS2-only. Rust withdrawals don’t use per-variant listings: the cheapest available stack is sourced when the withdrawal is purchased.

Listings here carry no itemId: you named the item in the request, and every row belongs to it. id identifies the individual listing and is what you pass to a withdrawal. itemId appears on GET /client/market rows, where the response spans many items.

Rate Limits

Merchant Status	Limit
Verified	600 requests / min
Unverified	30 requests / min

Errors

Code	Key	When
14	`LISTING_NOT_FOUND`	Listings for the item couldn’t be loaded and there is no pool stock to return instead (HTTP 404)
1001	`VALIDATION_FAILED`	Neither `itemId` nor `marketHashName` sent, or another parameter is invalid (HTTP 400, details in `error.fields`)
1005	`RATE_LIMITED`	Rate limit exceeded (HTTP 429)
1007	`SYSTEM_MAINTENANCE`	Service is in maintenance mode (HTTP 503)
1102	`INVALID_TOKEN`	Client token is invalid or expired
1108	`MISSING_BEARER`	No `Authorization` header

Overview

Authentication

Client

Trading

Secure

Verification

Wallet

Ledger

Get Item Listings

Request

Query Parameters

Response

Rate Limits

Errors

​Request

​Query Parameters

​Response

​Rate Limits

​Errors

Request

Query Parameters

Response

Rate Limits

Errors