{ "timezone": "UTC", "serverTime": 1565246363776, "futuresType": "U_MARGINED", "rateLimits": [...], "exchangeFilters": [...], "symbols": [ { "symbol": "BTCUSDCPERP", "pair": "BTCUSDC", "contractType": "PERPETUAL", "status": "TRADING", "baseAsset": "BTC", "quoteAsset": "USDC", "marginAsset": "USDC", "pricePrecision": 2, "quantityPrecision": 3, "orderTypes": ["LIMIT", "MARKET", "POST_ONLY"], "timeInForce": ["GTC", "IOC", "FOK", "GTX", "GTD"] } ] }

Endpoint Security Types

NONE

Endpoint can be accessed freely

TRADE

Requires valid API-Key and signature

USER_DATA

Requires valid API-Key and signature

USER_STREAM

Requires valid API-Key

MARKET_DATA

Requires valid API-Key

TRADE and USER_DATA endpoints are SIGNED endpoints and require HMAC SHA256 signatures.

Request Format

All responses are returned in JSON format. Data is returned in ascending order (oldest first) unless noted otherwise.

GET endpoints

Parameters sent as query string

POST/PUT/DELETE

Parameters via query string, request body (x-www-form-urlencoded), or both

Timestamps

Milliseconds by default; microseconds with X-MBX-TIME-UNIT header

Timeout

10-second timeout for API processing

Authentication Header

API keys are passed via the X-MBX-APIKEY header. All SIGNED endpoints require a signature parameter and timestamp parameter. See the Authentication page for full details on HMAC and RSA signing.

Rate Limits

The Futures API enforces rate limits based on IP address (request weight) and account (order count). Different endpoints have different weights. Monitor the X-MBX-USED-WEIGHT-1M and X-MBX-ORDER-COUNT-10S response headers to track your usage.