Improved
`legs` on the order leg schema clarified as always null
7 days ago
The legs field on the order leg schema is now documented as always null for an order leg, since legs are not nested beyond one level. The field's type and runtime behavior are unchanged.
Broker API
POST /v1/trading/accounts/{account_id}/ordersGET /v1/trading/accounts/{account_id}/ordersGET /v1/trading/accounts/{account_id}/orders/{order_id}GET /v1/trading/accounts/{account_id}/orders:by_client_order_idPATCH /v1/trading/accounts/{account_id}/orders/{order_id}DELETE /v1/trading/accounts/{account_id}/ordersPOST /v1/trading/accounts/{account_id}/orders/estimationDELETE /v1/trading/accounts/{account_id}/positionsDELETE /v1/trading/accounts/{account_id}/positions/{symbol_or_asset_id}GET /v1/rebalancing/runsGET /v1/rebalancing/runs/{run_id}GET /v1/events/tradesGET /v2/events/trades
Trading API
POST /v2/ordersGET /v2/ordersGET /v2/orders/{order_id}GET /v2/orders:by_client_order_idPATCH /v2/orders/{order_id}DELETE /v2/positionsDELETE /v2/positions/{symbol_or_asset_id}