Spot API

New here? Set up authentication first.

All private endpoints require a signed request. Read the Authentication Guide before making your first call. Public endpoints (market data, orderbook) need no credentials.

---

API Version

The current Spot API is v4. All endpoints in this section are served under:

https://api.btse.com/spot/api/v4/

Legacy v3.3

The previous v3.3 Spot API is still available for existing integrations. It is documented in the interactive Spot (Legacy v3.3) API Explorer, and its OpenAPI spec can be downloaded from /specs/spot-rest.openapi.yaml. New integrations should use v4.

---

Environment

Product	Production	Testnet
Spot REST	https://api.btse.com/spot	https://testapi.btse.io/spot
Spot WebSocket	wss://ws.btse.com/ws/spot	wss://testws.btse.io/ws/spot
Spot OSS	wss://ws.btse.com/ws/oss/spot	wss://testws.btse.io/ws/oss/spot

The OSS (Order Stream Service) endpoint is used exclusively for Orderbook Incremental Updates.

Public market data (orderbook, ticker, OHLCV, etc.) is now served by the Markets API.

---

Rate Limits

Category	Per API	Per User
Query	15 req/s	30 req/s
Orders	75 req/s	75 req/s

Exceeding limits triggers a tiered block: 1 second → 5 minutes → 15 minutes. A Retry-After header is included in all 429 responses. See Rate Limits for the full mechanism.

---

Discovering Tradeable Pairs

Call Markets Information (no auth required) to get all available markets:

curl https://api.btse.com/public-api/market/v1/markets

Each entry includes the symbol name and trading constraints:

Field	Use
symbol	The market identifier to use in all API calls (e.g. BTC-USDT)
active	true if the market is currently open for trading
baseCurrency / quoteCurrency	The two currencies in the pair
minOrderSize / maxOrderSize	Size limits for orders
minPriceIncrement	Tick size — your price must be a multiple of this
minSizeIncrement	Lot size — your quantity must be a multiple of this

Symbol naming conventions

Product	Format	Example
Spot	BASE-QUOTE	BTC-USD, ETH-USDT
Futures (v3)	BASE-PERP	BTC-PERP, ETH-PERP
Futures (legacy)	Concatenated	BTCPFC (use ApplyNewSymbolName: Y in FIX to get new names)

For crypto assets with very small prices, market data uses a K/M/B prefix (e.g. K_PEIPEI), but wallet APIs always use the original name without prefix (matching the base field).

---

API Status Codes

See the shared Error Codes reference for HTTP status codes and internal API enum values.

---

API Enum

Order status codes, order type codes, and other numeric enums are documented in Error Codes → API Status Enum.