Self Trade Prevention (STP)

​

Overview

​

STP Modes

​

Usage

• Limit orders
• Market orders
• Stop-limit orders
• Stop-market orders
• OCO orders (One Cancels Other)
• Collateral orders

​

Example

{
  "market": "BTC_USDT",
  "side": "buy",
  "amount": "0.001",
  "price": "40000",
  "stp": "cb"
}

​

Supported Endpoints

• POST /api/v4/order/new (Limit orders)
• POST /api/v4/order/market (Market orders)
• POST /api/v4/order/stock_market (Stock market orders)
• POST /api/v4/order/stop_limit (Stop-limit orders)
• POST /api/v4/order/stop_market (Stop-market orders)
• POST /api/v4/order/bulk (Bulk limit orders — per order item)
• POST /api/v4/order/modify (Modify order)
• POST /api/v4/order/collateral/limit (Collateral limit orders)
• POST /api/v4/order/collateral/market (Collateral market orders)
• POST /api/v4/order/collateral/stop-limit (Collateral stop-limit orders)
• POST /api/v4/order/collateral/trigger-market (Collateral trigger market orders)
• POST /api/v4/order/collateral/oco (Collateral OCO orders)

​

Best Practices

1. Default Behavior: If no STP mode is specified, the system defaults to no, allowing self-trades.
2. Risk Management: For automated trading systems or when running multiple strategies, use cb or cn to prevent unintentional self-trades.
3. Market Making: When running market making strategies, consider using cn to maintain existing orders’ queue position.

​

Response Handling

• Orders canceled due to STP will have a “CANCELED” status
• Successfully placed orders will proceed with normal status progression