Trading
What this group covers
Trading endpoints accept signed actions for order placement, cancel, replace, conditional orders, and account trading state.
The endpoint list below is generated from the canonical OpenAPI specification and kept in sync through CI.
List trading accounts
Lists control-plane trading accounts for an owner wallet. The response can include both a 32-byte `accountIdHex` and a 20-byte `engineAccountHex`; use the engine account for balances, signed actions, BSL/FIX/FIXP, and private streams.
Create trading account
Create trading account
Get trading account
Get trading account
Patch trading account
Patch trading account
Revoke owner trading access
Revoke owner trading access
Cancel all orders for an owner
Cancel all orders for an owner
Transfer collateral between trading accounts
Transfer collateral between trading accounts
Cancel all orders for a trading account
Cancel all orders for a trading account
Get trading account balances
Get trading account balances
Get trading account positions
Get trading account positions
Get trading account orders
Get trading account orders
Get trading account fills
Get trading account fills
Get trading account balance events
Get trading account balance events
List conditional orders
List conditional orders
Delete conditional order
Delete conditional order
Place order through delegated order-entry path
Place order through delegated order-entry path
Cancel order through delegated cancel path
Cancel order through delegated cancel path
Replace order through delegated batch path
Delegated replace uses the same signed batch envelope as `/api/v1/trading/orders/batch`; include one cancel/amend/place item as needed.
Submit batch trading actions
Submit batch trading actions
Submit batch cancels
Submit batch cancels
List open orders
List open orders
List historical orders
List historical orders
List fills
List fills
Submit signed trading action
Canonical mutating trading endpoint. Supports `Idempotency-Key` and recommends it for safe retries.
Compute trading action signing hash
Compute trading action signing hash
Reserve nonce range (deprecated)
DEPRECATED. Nonce reservations existed to escape the old strict-contiguous nonce rule. Under windowed replay protection any unused nonce in [nonceFloor, nonceFloor + nonceWindow) is accepted (gaps / out-of-order allowed), so reservations are no longer required. Retained for backward compatibility; new integrations should omit nonceReservationId and pick in-window nonces directly.