Skip to main content

Overview

Traders are automated trading bots that execute strategies on connected exchanges. Each trader runs as an isolated container (pod) with its own configuration, API server, and webhook system.

Trader Lifecycle

1

Create an empty trader

Creates a trader with sensible defaults: dry_run: true, API server enabled, stressShield active.
2

Assign exchange, strategy, and pair handling

Patch with exchangeId, strategyId, handling (pair list method), and plugins.
3

Start the bot

Patch with running: true. A container (pod) is spawned and begins trading.
4

Monitor and control

Use pod API commands (ping, status, balance, profit, etc.) to manage the running bot.

Step 1: Create Trader

Response

Step 2: Configure Trader

Assign an exchange, strategy, pair handling method, and plugins:
Response

Pair Handling Methods

Plugins

Step 3: Start Trading

Response

Pod Commands

Once running, send commands to the trader’s pod via the API:

Available Commands

Example: Check Profit

Response

Stop Trading

Pod Events (Webhooks)

The trader pod sends real-time events via webhooks. Query events for a trader:
Response

Stress Shield

The stressShield feature monitors market stress signals and can automatically pause trading during high-volatility events:
When enabled, the trader receives strategy_msg webhooks from the stress monitoring system.

Key Fields