API
ReferenceTrading

Your backpack

GET
/public/v1/backpack

Your on-site items, paginated. Each row's id is the backpack item id, the value you pass to withdraw. trade_locked_until is set while Steam's trade hold applies. Optional app_id and search filters.

Authorization

apiKey
AuthorizationBearer <token>

API key generated from your account settings on the website. Send as Authorization: Bearer csd_....

In: header

Query Parameters

page*string
Match^[1-9]\d*$
limit*string

Value in

  • "5"
  • "10"
  • "25"
  • "30"
  • "50"
  • "100"
app_id?string
Match^[1-9]\d*$
search?string
Length1 <= length <= 200

Response Body

application/json

curl -X GET "https://example.com/public/v1/backpack?page=string&limit=5"
{  "items": [    {      "id": 1,      "app_id": 1,      "market_hash_name": "string",      "amount": -9007199254740991,      "commodity": true,      "market_price": -9007199254740991,      "trade_locked_until": "2019-08-24T14:15:22Z"    }  ],  "metadata": {    "total_pages": -9007199254740991,    "total_items": -9007199254740991,    "current_page": -9007199254740991,    "current_limit": -9007199254740991  }}

Your Steam inventory GET

What is currently in your Steam inventory for one game, ready to be sold here. Each row carries a `token`: an opaque, signed handle for that item which you hand to `POST /public/v1/sell`. Tokens are tied to your account and expire after 30 minutes, so fetch, decide and sell in one pass rather than storing them. `amount` is how many copies that stack holds, and `tradable` is false while Steam is holding the item. This reads live from Steam, so it is heavily rate-limited.

Buy listings POST

Buys the listings named in the request in a single atomic call. Nothing is bought unless every line succeeds. `max_price` is a ceiling in cents, not an exact match: a listing that got cheaper between your quote and this call still fills, one that got more expensive fails with `LISTING_PRICE_CHANGED`. Set it high to opt out. This does not read or modify your cart, so a bot and a browser session on the same account never interfere with each other. Private listings are not in any feed and are bought by passing the `private_token` from the share link on that line. Without it the line comes back as `LISTING_NOT_FOUND`, the same as an id that does not exist.