JSON-RPC Envelope

The Derive v3 API is JSON-RPC 2.0. Every method — market data, trading, account, vaults — shares one request/response envelope and is reachable over two transports: a persistent WebSocket connection or a single HTTP POST. The method name and its params are identical across both; only the framing differs.

The envelope

A request carries an id, the protocol version, the method path, and a params object.

{
  "id": "1",
  "jsonrpc": "2.0",
  "method": "private/cancel",
  "params": {
    "subaccount_id": 12345,
    "instrument_name": "ETH-PERP",
    "order_id": "b7e6...c2a1"
  }
}

A response is either a result or an error — never both — and echoes the request id.

{
  "id": "1",
  "jsonrpc": "2.0",
  "result": {
    "order_id": "b7e6...c2a1",
    "instrument_name": "ETH-PERP",
    "order_status": "cancelled"
  }
}

{
  "id": "1",
  "jsonrpc": "2.0",
  "error": {
    "code": -32602,
    "message": "Invalid params",
    "data": "order_id not found"
  }
}

Get Started

Authentication & Keys

Trading Concepts

Permissionless Vaults

WebSocket

Reference

The envelope

​The envelope

The envelope