Value of your listings
What your active listings are worth at their asking prices: total_value in cents, across listing_count listings holding item_count items. Optional app_id filter. The v1 equivalent was ISales/GetActiveListingsValue.
Authorization
apiKey API key generated from your account settings on the website. Send as Authorization: Bearer csd_....
In: header
Query Parameters
^[1-9]\d*$Response Body
application/json
curl -X GET "https://example.com/public/v1/my-listings/value"{ "listing_count": -9007199254740991, "item_count": -9007199254740991, "total_value": -9007199254740991}List items for sale POST
Puts backpack items on the market. Each group in `listings` becomes one listing at the given `price` in cents; `items` holds backpack item ids (the `id` from `GET /public/v1/backpack`) with the quantity of each to sell. Identical commodity items grouped together sell as one stack. A commodity backpack row is a quantity rather than a single copy, so the same `id` may appear in several groups — that is how you get separate listings for copies of one item at the same price; the groups draw from one pool, and asking for more than the row's `amount` in total fails with `INSUFFICIENT_ITEMS`. At most 50 groups per request, 50 items per group. Auto-decaying prices are website-only. To sell something still sitting in Steam, use `POST /public/v1/sell` instead. Accounts have a ceiling on how much they can have listed at once; past it, listing fails with `LISTING_LIMIT_REACHED`. Contact support if you are hitting it.
Your listings GET
Your own listings, newest first, filterable by `app_id` and `status` (`ACTIVE`, `DISABLED`, `FILLED`). `available_amount` is how many more copies of a commodity listing you still hold in your backpack. Rows are lean: item detail for a listing is in `GET /public/v1/listings`.