Authenticated command to submit a new order against available liquidity or an open RFQ.
Authenticated channel. Connect to: wss://wss.prime.kraken.com/ws/v1
Command used to submit a new order either against any provided liquidity or an open RFQ. Results of this command will be visible in the ExecutionReport and Trade streams which will track the lifecycle of the order.
Order limit price. Required when OrdType is Limit. Optional when OrdType is RFQ — include it only to validate against a limit price; if omitted, the order executes at the quoted price.
Specifies how long the order remains in effect. Possible values: GoodTillCancel, FillAndKill, FillOrKill. RFQ orders are always executed as FillOrKill; you may omit this field and the platform applies that behavior.
Strategy-specific parameters. Required keys depend on Strategy — see Supported Order Strategies below. For SteadyPace, ClipSize and ClipInterval are required.
Use this for a standard resting limit order with no algorithmic strategy:
Accept an open quote by sending NewOrderSingle with OrdType set to RFQ. Use QuoteID and RFQID from the latest Open update on the Quote stream. Price is optional — omit it to trade at the quoted price, or set it to enforce a limit.
Send NewOrderSingle with OrdTypeRFQ, QuoteID and RFQID from the Open quote, matching Side/Symbol/OrderQty, and optional Price if you need limit validation. RFQ orders are always executed as FillOrKill — you may omit TimeInForce.
Monitor execution and trade streams for fill or reject. The quote moves to Filled when accepted.
Command requests do not return a direct ack; results arrive on the subscribed streams. Quotes expire at ValidUntilTime unless you accept them with NewOrderSingle or cancel the quote with Quote Cancel Request.
The Limit Example tab above omits Strategy entirely — suitable for a single resting limit order. Set Strategy when you need algorithmic execution; each strategy requires its own Parameters fields.
A schedule-based algorithm that divides an order into suborders (clips) and submits them at equal, user-defined intervals.Required parameters:
Parameter
Type
Description
ClipSize
Qty
Quantity sent on each clip (must be less than total OrderQty).
ClipInterval
string
Interval between clips (e.g. 1m, 30s).
Optional parameters:
Parameter
Type
Description
StartTime
string
ISO-8601 UTC time when the schedule begins sending clips.
EndTime
string
ISO-8601 UTC expire time for the order.
Variance
decimal
Randomization factor applied to clip sizes.
ErrorAction
string
Behavior when a clip fails (e.g. Pause).
Omitting ClipSize or ClipInterval while Strategy is SteadyPace produces an incomplete request. Use the SteadyPace Example tab above for a copy-paste-ready payload.