Trading Pairs

Answers "what can I trade?": every pair the Wellat platform supports, with the Binance sizing constraints an order must satisfy, plus the timeframes accepted by the chart price stream.

GET /bot/v1/spot/pairs

Signed like every other route (see Authentication), rate-limited under the read bucket (60 req / 10 s per key). No parameters and no request body — the list is global, not per-strategy.

Response

The standard success envelope; data carries the timeframe allowlist and the array of pairs:

{
  "status": true,
  "message": "Trading pairs retrieved",
  "data": {
    "timeframes": ["1s", "1m", "3m", "5m", "15m", "30m", "1h", "2h", "4h", "6h", "8h", "12h", "1d", "3d", "1w", "1M"],
    "pairs": [
      {
        "symbol": "BTCUSDT",
        "baseAsset": "BTC",
        "quoteAsset": "USDT",
        "status": "TRADING",
        "isSpotTradingAllowed": true,
        "orderTypes": ["LIMIT", "LIMIT_MAKER", "MARKET", "STOP_LOSS_LIMIT", "TAKE_PROFIT_LIMIT"],
        "supportedBotOrderTypes": ["MARKET", "LIMIT", "STOP_LOSS", "STOP_LOSS_LIMIT"],
        "filters": {
          "minPrice": "0.01000000",
          "maxPrice": "1000000.00000000",
          "tickSize": "0.01000000",
          "minQty": "0.00001000",
          "maxQty": "9000.00000000",
          "stepSize": "0.00001000",
          "marketMinQty": "0.00000000",
          "marketMaxQty": "78.32180226",
          "marketStepSize": "0.00000000",
          "minNotional": "5.00000000",
          "maxNotional": "9000000.00000000"
        }
      }
    ]
  }
}

Field reference

Field	Meaning
`timeframes`	Every candle interval the chart price stream accepts.
`symbol`	Binance pair symbol you submit in an order body, e.g. `BTCUSDT`.
`baseAsset` / `quoteAsset`	The two legs of the pair.
`status`	Binance symbol status. Only `TRADING` pairs are served.
`orderTypes`	Every order type Binance accepts for the pair.
`supportedBotOrderTypes`	The subset you may actually submit through `/orders`. Use this, not `orderTypes`.
`filters`	Binance order constraints; a null value means Binance did not publish that filter.

Filter semantics (all values are decimal strings, as Binance reports them):

minPrice / maxPrice / tickSize — price must be a multiple of tickSize within the min/max bounds.
minQty / maxQty / stepSize — quantity must be a multiple of stepSize within the bounds.
marketMinQty / marketMaxQty / marketStepSize — the same three, applied to MARKET orders only.
minNotional / maxNotional — bounds on price × quantity.

👍
Everything in the response is tradable
Every pair served is in TRADING status, spot-enabled, and accepts at least one submittable order type. Non-tradable pairs are filtered out server-side — there is nothing to skip on your end.

Freshness

🚧
Cached for 30 minutes
The response is cached server-side for 30 minutes, so a newly listed pair can take up to 30 minutes to appear. Cache it on your side too — the payload is large and changes only when a token is onboarded. Refreshing every 30–60 minutes is plenty.

The list is not authoritative for execution: every order is re-validated against live Binance exchangeInfo when it executes. Use this endpoint to discover symbols and size orders; expect an order to be rejected at execution if the pair's live constraints have moved.

Next: Chart Price Stream — live candles for these pairs.