Skip to main content

​
Endpoints

​
Order Entry

MethodEndpointDescription
POST/v1/trading/ordersInsert a single order
POST/v1/trading/orders/listInsert multiple orders (batch)
POST/v1/trading/orders/previewPreview order before submission

​
Order Modification

MethodEndpointDescription
POST/v1/trading/orders/replaceReplace/modify a single order
POST/v1/trading/orders/replace/listReplace/modify multiple orders (batch)

​
Order Cancellation

MethodEndpointDescription
POST/v1/trading/orders/cancelCancel a single order
POST/v1/trading/orders/cancel/listCancel multiple orders (batch)

​
Order Query

MethodEndpointDescription
POST/v1/trading/orders/openGet open orders

​
Order Types

TypeDescription
LIMITLimit order at specified price
MARKET_TO_LIMITMarket order that converts to limit
STOPStop order
STOP_LIMITStop-limit order

​
Order Lifecycle

Orders progress through these states: 
NEW → PARTIALLY_FILLED → FILLED
         ↓
      CANCELED
Real-Time Order UpdatesAfter submitting orders via REST, use the gRPC Order Stream to receive real-time updates on order status, fills, and cancellations. This is more efficient than polling for order status.

​
Time in Force

TIFDescription
DAYGood for the trading day
GTCGood till canceled
IOCImmediate or cancel
FOKFill or kill

​
Best Practices

  1. Use Order Stream for updates - Don’t poll for order status; use streaming
  2. Include client order ID - Use clOrdId for your own order tracking
  3. Preview before submit - Use the preview endpoint for order validation
  4. Handle rejects - Implement proper error handling for rejected orders