Futures API

New here? Set up authentication first.

All authenticated Futures endpoints require Read, Trading, or Transfer permission. Read the Authentication Guide before making your first call.

---

API Version

The current Futures API is v3. All endpoints in this section are served under:

https://api.btse.com/futures/api/v3/

Legacy v2.3

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

---

Environment

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

The OSS (Order Stream Service) endpoint is used exclusively for Orderbook incremental update streams.

---

Rate Limits

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

Rate limit violations trigger a tiered block: 1 second → 5 minutes → 15 minutes. A Retry-After header is included in 429 responses. See Authentication → Rate Limits.

---

Spam Order Policy

Orders with a notional value below 5 USDT are marked as spam orders:

• Spam orders are hidden and always pay taker fee.
• Post-Only API spam orders are rejected.
• Accounts placing ≥ 4 resting orders with total size < 20 USDT risk being flagged.
• Flagged accounts may face rate limits, position limits, or disabled API access.

---

Symbol Naming (v3)

Format	Example	When used
New	BTC-PERP	Default in v3 REST
Old	BTCPFC	FIX API legacy — use ApplyNewSymbolName: Y in Logon to use new names

---

Error Codes

See the shared Error Codes reference for HTTP status codes and API status enums.