CS2 Third-Party Markets Setup Guide

Time: 15 minutes | Difficulty: Advanced | Market: Gaming Mode: Full automation (conditional) | API: Varies by platform (REST APIs) | Docs: Platform-specific (see below)

This guide wires a CS2 skin trading bot to third-party marketplace APIs using the botwir3 runtime. Configure API credentials for Skinport, DMarket, or other CS2 markets, and run automated skin trading strategies locally.

⚠ Access requirements

CS2 skin trading operates across multiple independent third-party marketplaces. Each has its own API, terms, and restrictions:

Each sub-platform has independent terms of service, API access requirements, and rate limits. Verify the specific platform's terms before deploying.

⚠ Steam Marketplace. The Steam Community Market API is read-only. Automated purchasing on the Steam Marketplace is restricted by Steam's Subscriber Agreement. This guide covers third-party markets, not the Steam Marketplace directly. See the Steam Signal Monitor guide for Steam-specific data access.

The user is responsible for obtaining appropriate access and complying with all applicable platform terms.

Before you start

Verify that automated operation is permitted under the specific third-party marketplace's current terms of service before deploying. botwir3 provides tools for building structured automation. The user is responsible for compliance with the platform's terms and all applicable regulations.

Platform Terms: Skinport ToS | DMarket ToS | Last verified: May 2026

What you need

• An account on the target CS2 marketplace (Skinport, DMarket, etc.)
• API access or credentials from the platform
• The botwir3 runtime downloaded and unzipped
• A strategy config file from the builder

Step 1: Create API credentials

The process varies by platform:

Skinport:

1. Log in to skinport.com
2. Navigate to account settings or developer section
3. Generate or locate API credentials

DMarket:

1. Log in to dmarket.com
2. Navigate to Settings → API or the developer portal
3. Generate API keys

Permissions required: Varies by platform. Typically includes read (listings, pricing) and trade (buy, sell, exchange) access. Permissions to disable: Withdrawal permissions where available. Limit API scope to trading operations.

🔒 Security. API keys are platform-specific and scoped to the authenticated account. Keys are stored in a local config file and are not transmitted to botwir3 or any third party. botwir3 never sees, stores, or has access to platform credentials.

Step 2: Configure the adapter

Create adapter.json in the bot directory. Example for Skinport:

{
  "adapter": "cs2_market",
  "credentials": {
    "platform": "skinport",
    "api_key": "paste-api-key-here",
    "api_secret": "paste-api-secret-here"
  },
  "game": "cs2",
  "environment": "live",
  "rate_limit_ms": 2000
}

For DMarket:

{
  "adapter": "cs2_market",
  "credentials": {
    "platform": "dmarket",
    "api_key": "paste-api-key-here",
    "api_secret": "paste-api-secret-here"
  },
  "game": "cs2",
  "environment": "live",
  "rate_limit_ms": 2000
}

API keys are stored in a local config file on the machine running the bot. They are not transmitted to botwir3 or any third party. botwir3 never sees, stores, or has access to platform credentials.

Step 3: Test the connection

botwir3 test --adapter cs2_market

Expected output:

[botwir3] Adapter: cs2_market
[botwir3] Platform: skinport
[botwir3] Connection: OK
[botwir3] Permissions: read, trade
[botwir3] Rate limit: per platform documentation

Step 4: Start the bot

botwir3 start --config my-strategy.json

The runtime loads the strategy, computes the spec hash, connects to the configured CS2 marketplace API via the local credentials, and begins evaluating signals. The gate function compares proposed actions against the configured spec. The user is responsible for monitoring the bot and verifying execution outcomes.

Rate limits and considerations

Common CS2 market bot configurations include cross-platform arbitrage (identifying price differences between Skinport, DMarket, and Buff163), float value sniping (buying skins with specific wear patterns at market price), and inventory repricing for seller accounts. All actions and decisions are recorded in the local ledger.

Troubleshooting

Related guides

• Steam Signal Monitor Setup Guide — gaming, signal-only (Steam Market data)
• Shopify Setup Guide — e-commerce, seller-side automation
• TCGPlayer Setup Guide — collectibles, card marketplace automation

One bot. $129. No subscription. No $749/mo platform. → Build for CS2 Markets