The API your clients will use.

REST API — most-used endpoints

Every deployed instance exposes the same paths, signing scheme and response shapes — one shard or forty. Public market data is no-auth and CORS-enabled; order and account routes are HMAC-signed per client. Full route table in the OpenAPI spec.

EXAMPLE — SUBMIT A LIMIT ORDER

# Submit a limit buy order
curl -X POST https://api.basispoints.net/v1/orders \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_KEY' \
  -d '{
    "client_id":   "your-uuid",
    "symbol":      "BTC-PERP",
    "side":        "buy",
    "order_type":  "limit",
    "price":       "69500.00",
    "quantity":    "0.5",
    "tif":         "gtc",
    "margin_mode": "cross",
    "leverage":    10
  }'

WebSocket channels

One connection, multi-channel subscribe. Your terminals subscribe to public market data channels; ops tools tail private ops events in real-time; risk engines consume account_update / liquidated / margin_warning streams. private.{client_id} requires an HMAC-signed upgrade.

EXAMPLE — SUBSCRIBE TO BOOK + PRIVATE FEED

// Subscribe to BTC-PERP order book + your private channel
const ws = new WebSocket('wss://api.basispoints.net/ws')

ws.onopen = () => {
  ws.send(JSON.stringify({ action: 'subscribe', channel: 'orderbook.BTC-PERP' }))
  ws.send(JSON.stringify({ action: 'subscribe', channel: 'private.' + clientId }))
}

ws.onmessage = (ev) => {
  const e = JSON.parse(ev.data)
  switch (e.type) {
    case 'orderbook':       /* { symbol, bids, asks, seq } */         break
    case 'fill':            /* { order_id, price, quantity, fee } */  break
    case 'account_update':  /* { balance, available, equity, ... } */ break
    case 'liquidated':      /* { symbol, size, pnl, ... } */          break
  }
}

FIX 4.4 Gateway — Institutional

For institutional flow from your buy-side clients or your own hedging systems, every deployment ships with a FIX 4.4 acceptor over TCP. Translates to the same binary submit / cancel path as the REST and WS surfaces, with full session-level reliability (heartbeats, sequence recovery, resend).

Evaluating the stack? Book a technical deep-dive — we'll walk your engineering team through the full message set, session credentials, and onboarding checklist.