As soon as Kraken Trading Engine accepts the order, all order responses will be sent using the Execution Report message. This includes any fills, order status changes and confirmation of cancellation.Documentation Index
Fetch the complete documentation index at: https://kraken-sandbox.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
35=
8Unique identifier of the order.
ClOrdID of the previous action on this order.Condition: ExecType = Cancel
Unique identifier for each execution report message.
Unique order identifier generated by Kraken.
Sequence number for every ExecType=Trade. This ID is unique by pair.Condition: ExecType = Trade
Time of event expressed in UTC. Format:
YYYYMMDD-HH:MM:SS.uuuThe execution model of the order. For triggered orders, after the trigger the OrderType will reflect the new execution model of the order (market or limit).Possible values:
1: market2: Limit3: Stop-loss4: Stop-loss-limitR: Take-profitT: Take-profit-limitU: Trailing-stopV: Trailing-stop-limit
Side of the order.Possible values:
1: Buy2: Sell
Pair in the format BASE/QUOTE.
Limit Price of the order placed in the Order Book. This field is denominated in Quote Currency.Condition: OrderType = Limit / Stop-Loss-Limit / Take-Profit-Limit / Trailing-stop-limit
Stop Price for a Stop-Loss / Take-Profit / Stop-Loss-Limit or Take-Profit-Limit order. This field is denominated in Quote Currency.Condition: OrderType = Stop-Loss / Take-Profit / Stop-Loss-Limit / Trailing-stop / Trailing-stop-limit
Price of the trade.Condition: ExecType = Trade
Avg price of all trades on the order.Condition: ExecType = Trade
Price that triggered for stop-loss, take-profit, stop-loss-limit, take-profit-limit, trailing_stop or trailing_stop_limit. It can be different than the StopPx.
Total quantity filled on the order so far.
Quantity bought/sold on last trade.Condition: ExecType = Trade
Quantity left on the order on the Book.
Size of the original order.
Iceberg qty of the original order.
Describes the type of order event and determines the set of fields in the message.Possible values:
0: New — Order has been created and is live in the engine.4: Canceled — The order has been cancelled.5: Replace — The order has been replaced.A: Pending New — Order request has been received and validated but the order is not live yet. Possible when EffectiveTime (Tag 168) is used on the New Order.C: Expired — The order has expired.D: Restated — The order has changed like a trigger event.F: Trade — The order has received a fill.I: Order Status — In response to an Order Status Request.
Describes the status of the order.Possible values:
0: New — Order is live in the engine with no fills.1: Partially Filled — Order is live in the engine with fills.2: Filled — Order is fully filled and closed.4: Canceled — Order is cancelled and closed.5: Replaced — Order is Replaced successfully.A: Pending New — Order is not live yet. For example when EffectiveTime is used.C: Expired — Order is expired and closed.E: Pending Replace — New parameter of the replace are not live yet. For example when EffectiveTime is used or a trade was in flight during the replace request.
Full description for Cancellations or status of the order.
Possible values:
1: GTC (Good till canceled)3: IOC (Immediate or Cancel)4: FOK (Fill or Kill)6: GTD (Good till date)
1 where a fee is applicable or not present.Cum Cost of the Trade (CumQty × AvgPx).
Cost of a Single Trade (LastQty × LastPx).
Unique ID that identifies the trade at exchange.Condition: ExecType = Trade
Define if the trade was from a maker or taker order.Possible values:
0: Maker1: Taker
Number of subaccount that are part of the order. Always 1 for the broker accounts.
It can happen in some scenario that trades are not reported in time through the FIX API.
In that case the FIX API will detect it and send a ExecType=Restated execution report and use ExecRestatementReason to warn the client.Possible values:
3: Repricing of Order
- Spot
- Futures
Other states
Other states