Skip to main content
Merchant lots are for a seller with stock in several Steam accounts and software of his own that sends trade offers. You send us lots; we put them on the CSBoard P2P market; when one is bought we call your server; you send the Steam offer and tell us what happened to it. You do not connect any Steam account to CSBoard and we do not ask for a login or an API key of your accounts. Each lot names the trade link of the account it sits in: our bots look into the account through it.
Off by default. Write to us to have it switched on for your merchant account. Then set it up yourself: in the merchant portal, under Developers → Merchant lots, save the three URLs described below. The first save shows your app secret once; New secret replaces a lost one, and the old one stops working at once.

The numbers

Only items that can be traded right now are accepted (assetType: 1).

Three URLs on your side

All three are POST with a JSON body. You have 5 seconds to answer Order Create (3 seconds when the buyer comes from a partner market). No answer in time means the purchase does not happen, so the same item listed on several markets cannot be sold twice: every sale asks you first.

Verifying our calls

Every body carries sign: take every other field, sort by name, join as name=value with &, append &sign=<your app secret>, MD5, upper case. A null value is the string null.
The same body is also signed in the X-CSBoard-Signature header (t=<unix>,v1=<hex>, HMAC-SHA256 of <t>.<raw body> with the same secret), exactly like our webhooks.

How a sale goes

1

List the lots

productId is your own id for the lot. tradeUrl is the trade link of the same account as steamId; send the current one with every lot, we keep the latest. delivery is 1 when you send the offer by hand and 2 when your bot sends it right after our order call: a 2 lot is shown to buyers as instant and has 10 minutes to send. Up to 100 products per call. A product we cannot take comes back in errorData.failList with its reason; the others are accepted.A lot is not on sale yet. We first read the Steam account’s public inventory ourselves and list the lot once we have seen the item there. Follow it with GET /p2p/sell/detail/{productId}: operationStatus goes 100 (listing) to 101 (listed) or 102 (failed, with failedCode).
2

Take the order

We call your Order Create URL with requestId (our id for the sale, use it in every report), your productId, payPrice and the buyer’s tradeUrl. Answer status: 1 and send the Steam offer to that trade link.
3

Report every status

Send one each time the status changes. Repeating a report is safe.tradeOfferId is Steam’s own tradeofferid of the offer you sent for this order. It is required with 2, 3 and 10 unless you already reported it, one order has one offer, and we look that offer up on Steam by it.
4

Get paid

GET /p2p/sell/order/list shows every sale with our orderStatus, our fee and settleTime, the moment it pays to your balance.

Order statuses

tradeOfferStatus is Steam’s own ETradeOfferState. What we do with a report:
  • 10 is acknowledged like every status, and then we check it ourselves: the offer you named, read on Steam by its tradeOfferId from the buyer’s side, or else the item gone from the seller account (its public inventory and its trade window, read through the lot’s tradeUrl). Until we have seen it the answer’s data is checking and the order stays at 3 in GET /p2p/sell/order/list. You do not send it again: we look again by ourselves every few minutes.
  • 11 after an offer never closes the sale on your word alone: we look for the item back in the seller’s inventory first.
  • 220 with reversedType: 2 puts the sale on hold for a manual review. It does not pay.

The Steam refresh token

Add refreshToken to a status report to let us read that one trade on Steam:
  • It must be the mobile refresh token of the Steam account that sent the offer.
  • We use it for one read and discard it. It is not stored and not logged, and we never ask Steam to renew it, so your copy stays valid.
  • With 10 we check the offer carries the sold item and was accepted by this sale’s buyer. With 200, sent after Steam’s protection has ended, we read the trade: complete means the sale is paid now; reversed means it is settled as a reversal.
  • The answer tells you what the read proved in tokenRead: accepted, complete, reversed, not_final (too early, send 200 again later), mismatch (another account’s token, or an offer or trade that does not give this sale’s item to this sale’s buyer), token_refused, unreadable.
The token is optional. Without it the sale pays on day 14. Keep the seller account’s inventory public until the sale is paid. On day 14 we look at it once more; if we cannot read it, the payout waits and we look again every hour.

Managing lots

Lot status: 1 selling, 2 cancelled, 3 hidden (we stopped seeing the item in the account; it returns by itself), 4 in a trade, 5 sold. A price under half of our market price is refused with price_below_market, as for any P2P listing.

Answers

Every answer has the same shape:
On a refusal success is false, errorCodeStr is the code to branch on and errorMsg says it in words.