Skip to main content
To sell on P2P, you read your Steam inventory, list items with the key it returns, and keep the extension running so it can send the Steam offer when an item sells.
Every route on this page needs the seller’s extension running. Without it, listing fails with extension offline and existing listings leave the catalog.

Inventory

GET /p2p/inventory/{game} returns the Steam items you can list. Items already listed, reserved, or paused are left out.
Response
Each group in informations matches a deposit row: assetid values separated by ;, depositkey as { "assetId": "key" }, item_id, and catalog.

List

POST /p2p/list lists one asset.
Response: { "listing": { }, "sold": false }.
sold: true plus a trade object means a buy order already covered your price. The item is sold, the buyer’s balance is debited, and the extension must send the Steam offer.
You can have at most 500 active listings.

Unlist

POST /p2p/unlist removes a listing.
Allowed while the listing is for sale or paused. Rejected with listing reserved once a sale is in progress.

Change the price

POST /p2p/listing/price reprices a listing.
Works only on a listing that is for sale.
  • Dropping the price to a buy order sells the item immediately (sold: true + trade).
  • Dropping the price to a pending offer’s price cancels that offer.

My listings

GET /p2p/listings/mine returns your listings.
Response
Items are grouped like the catalog: count, ids (listing ids separated by ;), and listing_keys. To unlist or reprice, use one listing_id from the group. Filter with state, for example ?state=5. By default the list contains states 0, 1, and 5.

Price history

GET /item/salesGraph/p2p/{item} returns P2P sale history. {item} is the catalog id or the slug. period is required: 1M, 3M, 6M, 1Y, 5Y, or ALL.

Next steps