
KarambitDoppler
b2b skins api for case sites
skin supply for case opening, upgrade and battle sites. source cs2, dota 2 and rust inventory; deliver cs2 withdrawals and accept cs2 skin deposits through one api.
bring supplier inventory into your storefront. real prices, live availability, no stock to manage.

KarambitDoppler

AWPAsiimov

Sport GlovesVice
send a cs2 item straight to your user’s steam trade url. follow the order from purchase to delivery.
your product
player’s inventory

let users sell cs2 skins through your product. get a quote, send a trade, track settlement.
2 items selected
credited after steam trade protection
merchant workspace
purchases, sales, balances and your team. the workspace behind every api call.
open merchant panelinterface preview: illustrative data
built for developers
start with the api docs. or give your coding agent the integration prompt, with endpoints and safeguards included.
integrate the csboard api into this project. read first: - https://csboard.com/cs2-skins-api/llms.txt - https://api.csboard.com/llms.txt - openapi spec: https://api.csboard.com/openapi.json - mcp server: https://csboard.com/mcp (streamable http, header "Authorization: Bearer $CSBOARD_API_KEY") my key is in the env var CSBOARD_API_KEY. base url: https://csboard.com/v1 build: 1. a catalog client on GET /v1/listings and GET /v1/prices (appId 730, 570, 252490). 2. a buy flow on POST /v1/market/buy with appId, partner, token, max_price_usd and a saved custom_id. successful responses are cached for up to 24 hours; the same id can buy again after expiry. if the outcome is unknown, use GET /v1/orders/info with custom_ids; do not send another buy or assume empty data means failure. 3. a webhook receiver that verifies X-CSBoard-Signature (hmac-sha256). 4. if sell access is enabled for the selected game: POST /v1/sell/quotes, then POST /v1/sell/orders with app_id and a saved external_id. catalog permission does not imply sell permission. track order status and settlement; receiving the Steam trade alone is not proof of credited balance. use the stack already in this repo and write tests.
POST /v1/market/buy
Authorization: Bearer $CSBOARD_API_KEY
Content-Type: application/json
{
"item_ids": ["<listing_id>"],
"partner": "<steam_partner_id>",
"token": "<trade_token>",
"max_price_usd": 120.00,
"custom_id": "your-order-1042"
}
example requestcs2 / 730for case opening sites
connect skin withdrawals to live inventory, price-protected purchases and tracked steam delivery. keep your game logic in your app; use csboard for fulfillment.
explore the cs2 skin fulfillment api ↗csboard aggregates 10 supplier feeds and csboard p2p sellers. /v1/listings shows catalog prices; price and availability are checked again when buying. send max_price_usd to limit your total spend. if the live price exceeds it, the api returns price_moved; review a fresh quote before deciding whether to buy.
send the form on this page or write to api@csboard.com. after a short review you get a merchant.csboard.com account with 2fa, and the key is in its developers tab. buying is a separate switch per key.
top up your csboard balance with usdt in the cabinet. api orders are debited from that balance. delivery to a third-party trade url is paid from settled balance only.
median 2m 16s from order to delivered, measured over 10,979 orders in the last 30 days. items inside a steam trade hold wait for the hold to end; each listing shows its delivery type before you buy.
cs2, dota 2 and rust (appId 730, 570 and 252490). delivery to another account’s steam trade url uses POST /v1/market/buy and requires enabled external delivery, trading access and permission for the selected game. dota 2 and rust orders start as pending; this does not mean delivered. instant sell access is enabled separately for each game. confirm game access when requesting your api key.
tell us what you are building and the volume you expect. we answer from api@csboard.com.
or write directly:
read the docs