Skip to main content

Trade

DLTF operates FIX Trading Gateways which allow users to manage orders on their DLTF Account using FIX 4.4 messages.

Connection validation

In order to activate the fix protocol, you need to provide us with the public key of your certificate, which you will use every time you connect to the FIX server. Example of certificate generation:

$ openssl genrsa -out example.key 2048

$ openssl req -new -x509 -sha256 -key example.key -out example.crt -days 3650

In result you will have 2 files: example.key and example.crt. example.key must be used for encrypt TLS connection to FIX server. example.crt must be provided to DLTF for connection validation.

Environments

DLTF operates both Production and Test environments which can be connected to using FIX using the following connection parameters.

DLTF Digital ServiceIP/DNSPortDLTF CompIdClient CompId
Testfix.stage.dltm.quanttradingfactory.com5000STAGE_DLTF<check details in client FIX settings>

Messages sizes

Inbound message size limit

The DLTF FIX Trading Gateways have a maximum inbound message limit of 8192 bytes. If a message is received which exceeds this size, the client will be logged off.

Outbound message size

The DLTF FIX Trading Gateway will never publish messages greater than 8192 bytes.

Recovery

FIX Session Recovery

The DLTF FIX Trading Gateways allow a client to recover the most recent 512 messages for a session using standard FIX message resend behaviour.

In the event of the DLTF FIX Gateway requesting a message re-send, the resent messages will be ignored to avoid out of date orders being placed into the market.

In some scenarios FIX session recovery is insufficient. Some examples would be:

  • More than 512 messages are queued for a particular session. In this case only the most recent 512 messages will be available for replay using FIX session recovery.
  • The DLTF FIX Trading Gateway that the session was running on fails. DLTF FIX Gateways do not support session failover. On reconnecting after a gateway failure, a client will be connected to a different gateway which will not have messages available for resending.
  • Access is required to historic data which is no longer available in the current FIX Sesssion due to a sequence number reset.

In these scenarios it will be necessary to use Application Recovery as described below. It may be simpler to ignore FIX session recovery entirely and always use Application Recovery as it will work in all failure scenarios. If this option is chosen then tag 141 (ResetSeqNumFlag) should always be set to "Y" on the client Logon message.

Application Recovery

DLTF FIX Trading Gateways accept two messages to enable a client to reliably recover after a disconnection. These are:

Message TypeDescription
Order Status RequestAllows a client to query the status of an Order.
Trade Capture Report RequestAllows a client to request historic trades.

Using these messages it is possible for a client to determine what trades occured on their Account during a disconnection and the current status of orders that were working at the time of the disconnection.

These messages may also be used to request historic data.

The sections on these two messages provide a detailed description on their usage.

Session Resetting

To reset a FIX Session the client must login with the tag 141 (ResetSeqNumFlag) set to 'Y'.

Cancel on Disconnect

DLTF supports cancel on disconnect on it's FIX Trading Gateways. This is controllable on a per Order basis using the Tag 18 (ExecInst) on the New Order Single (MsgType="D"). By default, orders placed via the FIX Trading Gateways will be cancelled on an explicit logout or an unexpected disconnection from the FIX Trading Gateway. To allow an order to continue working on the DLTF Order Book after the session is disconnected, the client must set Tag 18 (ExecInst) to "H" (Reinstate on System Failure).

Note that cancel on disconnect cannot be specified when a user is configured to trade on multiple accounts. In this case the user must always set Tag 18 (ExecInst) to "H" (Reinstate on System Failure).

Orders placed via the web channel (either the DLTF web trading user interface) will not be cancelled when a FIX Trading session logs out or is disconnected.

Compatibility

DLTF aims to maximise compatibility by using standard FIX messages, tags and usage conventions wherever possible.

Periodically, DLTF updates it's FIX specifications in response to changes to the core trading application. Usually these changes are to support additional features and wherever possible this will be achieved through the use of additional messages, tags in existing messages or tag values in existing tags. In order to minimise the impact of these sort of changes, DLTF recommends that the client application accepts messages with unrecognised tags and ignores those tags which it cannot interpret.

DLTF will always endeavor to contact clients prior to changing the FIX API particularly in the case where a change is breaking (i.e. not additive in nature).

Messages

Supported Messages

DLTF supports the following FIX message types.

TypeNameDescription
0HeartbeatMessage sent during quite intervals on the connection to ensure that connection is still alive.
1TestRequestMessage used to request a HeartBeat from the counterparty to allow round trip testing of the connection.
2ResendRequestMessage used to request a replay of messages from the counter party.
3RejectSent in response to a message which is structurally invalid (i.e. invalid or missing tag or ill-formed tag-value).
4SequenceResetSequenceReset.
5LogoutMessage used to terminate a FIX connection. Can be sent by the client or the DLTF FIX Gateway.
8ExecutionReportMesssage sent by the DLTF FIX Gateway which reports the change in status of a client's Order
9OrderCancelRejectMessage sent by the DLTF FIX Gateway when an OrderCancelRequest message cannot be successfully processed.
ALogonMessage used to establish a connection between a client and the DLTF FIX Gateway.
DNewOrderSingleMessage sent by the client to place a new order with DLTF.
FOrderCancelRequestMessage sent by the client to cancel an existing order which is working on an DLTF order book.
HOrderStatusRequestMessage sent by the client to request the state of an order.
ADTradeCaptureReportRequestMessage sent by the client in order to request historic trades.
AETradeCaptureReportMessage sent by DLTF to report an historic trade.
AQTradeCaptureReportRequestAckMessage sent by DLTF in response to a Trade Capture Report Request message to confirm the success or failure of the request.

Standard Message Components

StandardHeader

TagTag NameDescriptionRequiredData Type
8BeginStringThe FIX version number identifier. Always 'FIX.4.4'YString
9BodyLengthLength of the FIX Message.YLength
35MsgTypeThe type of the message.YString
49SenderCompIDIdentifier for the sender of the message.YString
56TargetCompIDIdentifier for the receiver of the message.YString
34MsgSeqNumThe unique sequence number for the message within current FIX session.YSeqNum
43PossDupFlagAlways required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. Set to 'Y' if this is a resent message.NBoolean
97PossResendNever used by DLTF.NBoolean
52SendingTimeTime message was sent.YUTCTimestamp
122OrigSendingTimeTimestamp when message was originally sent. Required for message resent as a result of a ResendRequest.NUTCTimestamp

StandardTrailer

TagTag NameDescriptionRequiredData Type
10CheckSumChecksum for message contents.YString

Instrument

TagTag NameDescriptionRequiredData Type
48SecurityIDMust contain the DLTF orderbook id. (temporary not supported)NString
22SecurityIDSourceMust contain the value '8' (Exchange Symbol) (temporary not supported)NString
55SymbolTicker symbol with / as delimeter (example: BTC/EUR)YString

OrderQtyData

TagTag NameDescriptionRequiredData Type
38OrderQtyThe number of contracts that an order is for.YQty

MiscFeesGrp

TagTag NameDescriptionRequiredData Type
136NoMiscFeesNumber of Fee fields provided in fees range. Must be 1.YNumInGroup
137MiscFeeAmtTrade fee value.YQty
138MiscFeeCurrTrade fee currency.YString
139MiscFeeTypeIndicates type of fee. Must be 8 (MARKUP)Ychar
891MiscFeeBasisDefines the unit for a fee. Must be 0 (ABSOLUTE)Yint

TrdCapDtGrp

TagTag NameDescriptionRequiredData Type
580NoDatesNumber of Date fields provided in date range. Must be 2.YNumInGroup
60TransactTimeStart (First entry in repeating group)or end (Second entry in repeating group) timestamp of the period for which trades should be retrieved expressed in UTC.YUTCTimestamp

TrdCapRptSideGrp

TagTag NameDescriptionRequiredData Type
552NoSidesNumber of Side repeating group instances. Valid values: 1 Contains information about the client Order which traded.YNumInGroup
54SideSide of the order. Valid values: 1 = Buy 2 = SellYchar
37OrderIDUnique identifier for Order as assigned by DLTF. Unique over all time and orderbooksYString
11ClOrdIDThe client supplied identifier for the order.NString
1AccountThe DLTF Account Id on which the trade occurredNString

Message Descriptions

Heartbeat

Message sent during quite intervals on the connection to ensure that connection is still alive.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 0
112TestReqIDRequired when the heartbeat is the result of a Test Request message.NString
StandardTrailerY

TestRequest

Message used to request a HeartBeat from the counterparty to allow round testing trip of the connection.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 1
112TestReqIDIdentifier included in Test Request message to be returned in resulting HeartbeatYString
StandardTrailerY

ResendRequest

Message used to request a replay of messages from the counter party.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 2
7BeginSeqNoMessage sequence number of first message in range to be resentYSeqNum
16EndSeqNoMessage sequence number of last message in range to be resent. If request is for a single message BeginSeqNo (7) = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = “0” (representing infinity).YSeqNum
StandardTrailerY

Reject

Sent in response to a message which is structurally invalid (i.e. invalid or missing tag or ill-formed tag-value).

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 3
45RefSeqNumMsgSeqNum of rejected messageYSeqNum
371RefTagIDThe tag number of the FIX field being referenced.Nint
372RefMsgTypeThe MsgType of the FIX message being referenced.NString
373SessionRejectReasonCode to identify reason for a session-level Reject message.Nint
58TextWhere possible, message to explain reason for rejectionNString
StandardTrailerY

SequenceReset

SequenceReset

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 4
123GapFillFlagIndicates that the Sequence Reset message is replacing administrative or application messages which will not be resent. Valid values: Y = Gap Fill message, MsgSeqNum field valid N = Sequence Reset, ignore MsgSeqNumNBoolean
36NewSeqNoNew sequence numberYSeqNum
StandardTrailerY

Logout

Message used to terminate a FIX connection. Can be sent by the client or the DLTF FIX Gateway.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 5
58TextIf DLTF logs out a client this may contain a text description for the reason for the logout.NString
StandardTrailerY

ExecutionReport

Messsage sent by the DLTF FIX Gateway which reports the change in status of a client's Order

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 8
37OrderIDThe unique identifier allocated by DLTF for the order whose execution is being reported.YString
11ClOrdIDThe client supplied identifier for the order whose execution is being reported.NString
41OrigClOrdIDConditionally required for response to an electronic Cancel or Cancel request (ExecType=PendingCancel or Canceled). ClOrdID of the previous accepted order (NOT the initial order of the day) when canceling or replacing an order.NString
790OrdStatusReqIDRequired if responding to and if provided on the Order Status Request message. Echo back the value provided by the requester.NString
17ExecIDThe unique identifier allocated by DLTF Broker to the ExecutionReport message.YString
150ExecTypeDescribes the type of execution being reported by this ExecutionReport message.Ychar
39OrdStatusDescribes the current state of a chain of orders.Ychar
103OrdRejReasonFor use with ExecType = 8 (Rejected). Contains the reason for the rejection.Nint
1AccountContains the DLTF Account Id for the account on which the order was placed.NString
InstrumentY
54SideSide of the order. Valid values: 1 = Buy 2 = SellYchar
OrderQtyDataY
40OrdTypeOrder type. DLTF Supported values: 1 = Market 2 = LimitNchar
44PricePresent if specified on the orderNPrice
59TimeInForceSpecifies how long the order remains in effect. Valid values: 1 = Good Till Cancel (GTC)Nchar
32LastQtyQuantity of contracts bought/sold on this fill. Will be present if ExecType = Trade.NQty
31LastPxPrice of this (last) fill.NPrice
151LeavesQtyQuantity open for further execution.YQty
14CumQtyCurrently executed quantity for chain of orders.YQty
6AvgPxAverage fill price for the chain of orders. Rounded down to the nearest price increment.YPrice
60TransactTimeTime the transaction represented by this ExecutionReport occurredNUTCTimestamp
58TextFree format text string (Note: this field does not have a specified maximum length)NString
1101CustomTagRepresent best bid price of orderbook on moment of trade execution (will be represented on ExecutionReport with ExecType = F (Trade)NString
1102CustomTagRepresent best ask price of orderbook on moment of trade execution (will be represented on ExecutionReport with ExecType = F (Trade)NString
1103CustomTagRepresent average value between best bid and best ask prices on moment of trade execution (will be represented on ExecutionReport with ExecType = F (Trade)NString
1104CustomTagRepresent value of cumulative order fees on moment of trade execution (will be represented on ExecutionReport with ExecType = F (Trade)NString
MiscFeesGrpY
StandardTrailerY

OrderCancelReject

Message sent by the DLTF FIX Gateway when an OrderCancelRequest message cannot be successfully processed.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= 9
37OrderIDThe OrderId of the Order which failed to be cancelled. If CxlRejReason=”Unknown order” this will be “NONE”.YString
11ClOrdIDThe client supplied identifier for the cancel request.YString
41OrigClOrdIDClOrdID which could not be canceled. ClOrdID of the previous accepted order (NOT the initial order of the day) when canceling or replacing an order.YString
39OrdStatusOrdStatus value after this cancel reject is applied. If (102) = "Unknown Order", specify Rejected.Ychar
1AccountThe DLTF Account Id on which the Cancel was attempted.NString
434CxlRejResponseToIdentifies the type of request that a Cancel Reject is in response to. DLTF Supported values: 1 = Order Cancel Request (F)Ychar
102CxlRejReasonCode to identify reason for cancel rejection. Valid values: 1 = Unknown order 2 = Broker / Exchange OptionNint
58TextFree format text string (Note: this field does not have a specified maximum length)NString
StandardTrailerY

Logon

The Logon message must be the first message Client sends after establishing a TCP connection on the port agreed upon with DLTF. Client must wait for a Logon from DLTF before sending other messages and beginning gap fill operations.

Password is represented as ed25519 signature of [payload].

Payload is composed of the following fields:

MsgSeqNum SENDERCOMPID TARGETCOMPID API_KEY NONCE

The nonce is integer (recommend to use nanoseconds timestamp), always increasing value.

Example:

payload := fmt.Sprintf("%d%s%s%s%d", seqNum, sender, target, pubKeyHex, time.Now().UnixNano()) signatureRaw := ed25519.Sign(privateKey, []byte(payload)) signatureHex := hex.EncodeToString(signatureRaw)

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= A
98EncryptMethodAlways '0' - NoneYint
108HeartBtIntThe maximum time to wait before a Heartbeat message is sent in the absence of other activity on the connection. The same value is used by both parties.Yint
141ResetSeqNumFlagIndicates both sides of a FIX session should reset sequence numbersNBoolean
553UsernameAPI Token public key in HEX format. This is required on the login message sent by the clientYString
554PasswordSignature in HEX format. This is required on the login message sent by the clientYString
5025NonceTime in ms since epoch as string. (This will be used in password generation and check)YString
StandardTrailerY

NewOrderSingle

Message sent by the client to place a new order with DLTF.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= D
11ClOrdIDThe client supplied identifier for the order.YString
100ExDestinationExecution destination as defined by DLTF when order is entered.YExchange
InstrumentY
1AccountThe DLTF Account ID on which to place the new order. If not specified then the user's default account will be used.NString
54SideSide of the order. Valid values: 1 = Buy 2 = SellYchar
18ExecInstInstructions for order handling on exchange trading floor. If more than one instruction is applicable to an order, this field can contain multiple instructions separated by space. Valid values: H = Reinstate on System Failure (Do not cancel on disconnect) Q = Cancel on System Failure (Cancel on disconnect)NMultipleStringValue
60TransactTimeTime this rder request was initiated/released by the trader, trading system, or intermediary. Ignored by DLTF.YUTCTimestamp
OrderQtyDataY
40OrdTypeOrder type.DLTF Supported values: 1 = Market 2 = LimitYchar
44PriceRequired for Limit OrdTypes.NPrice
StandardTrailerY

OrderCancelRequest

Message sent by the client to cancel an existing order which is working on an DLTF order book.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= F
41OrigClOrdIDClOrdID of the previous non-rejected order (NOT the initial order of the day) when canceling or replacing an order.YString
1AccountThe DLTF Account ID on which to attempt to cancel the order. If not specified then the user's default account will be used.NString
11ClOrdIDThe client supplied identifier for the order.YString
InstrumentY
54SideSide of the order.Valid values: 1 = Buy 2 = SellNchar
60TransactTimeTime this order request was initiated/released by the trader or trading system.YUTCTimestamp
OrderQtyDataY
StandardTrailerY

OrderStatusRequest

Message sent by the client to request the state of an order. Note that orders that were rejected for whatever reason will be reported as an unknown order.

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= H
11ClOrdIDThe ClOrdID of the order whose status is being requested.YString
1AccountThe DLTF Account ID on which the order whose state is being requested was placed. If not specified then the user's default account will be used.NString
790OrdStatusReqIDOptional, can be used to uniquely identify a specific Order Status Request message. Echoed back on Execution Report if provided. restricted to a maximum of 16 hexadecimal characters with no leading 0 characters (essentially this is a 64bit number).NString
InstrumentY
54SideSide of the order. Valid values: 1 = Buy 2 = SellYchar
StandardTrailerY

TradeCaptureReportRequest

The Trade Capture Report Request message is used by the client to request historic trades. In order to request historic trades the client provides the period of time for which trades are being requested. The period is specified using a start and end time. The gateway will response in one of the following ways: Scenario|Response An invalid request is made such as the start time is after the end time|The gateway sends a Trade Capture Report Request Ack message with the following tags set:

  • Tag 749 (TradeRequestResult): 99 (Other)
  • Tag 750 (TradeRequestStatus): 2 (Rejected)
  • Tag 58 (Text): contains an error message.

There are no trades in the requested period.|The gateway sends a Trade Capture Report Request Ack message with the following tags set:

  • Tag 748 (TotNumTradeReports): set to 0. Note that this is the only scenario in which this tag will be present in the Trade Capture Report Request Ack.
  • Tag 749 (TradeRequestResult): 0 (Successful)
  • Tag 750 (TradeRequestStatus): 0 (Accepted)

There are trades in the requested period.|The gateway sends a Trade Capture Report Request Ack message with the following tags set:

  • Tag 749 (TradeRequestResult): 0 (Successful)
  • Tag 750 (TradeRequestStatus): 0 (Accepted)

followed by a Trade Capture Report message for each Trade in the requested period. The last Trade Capture Report will have tag 912 (LastRptRequested) will be set to "Y".

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= AD
568TradeRequestIDTrade Capture Report Request ID. Must be unique string while a request is active.YString
569TradeRequestTypeType of Trade Capture Report. DLTF supported values: 1 = Matched trades matching Criteria provided on requestYint
263SubscriptionRequestTypeUsed to subscribe / unsubscribe for trade capture reports.DLTF supported values: 0 = SnapshotNchar
1AccountThe DLTF Account Id whose trades to request.NString
TrdCapDtGrpY
StandardTrailerY

TradeCaptureReport

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= AE
568TradeRequestIDTrade Capture Report Request ID as provided in the Trade Capture Report Request.NString
912LastRptRequestedIndicates if this is the last report in the response to a Trade Capture Report Request Y = Last message N = Not last messageNBoolean
17ExecIDExecution ID (Trade Identifier) as assigned by the DLTF Broker as reported on the original Execution Report (MsgType=8) message.NString
InstrumentY
32LastQtyTrade quantity.YQty
31LastPxTrade price.YPrice
75TradeDateTrade date on which the trade occurred.YLocalMktDate
60TransactTimeTime the transaction represented by this Trade Capture Report occurred to millisecond resolutionYUTCTimestamp
TrdCapRptSideGrpY
StandardTrailerY

TradeCaptureReportRequestAck

TagTag NameDescriptionRequiredData Type
StandardHeaderYMsgType= AQ
568TradeRequestIDTrade Capture Report Request ID as provided in the Trade Capture Report Request.YString
569TradeRequestTypeType of Trade Capture Report. DLTF supported values: 1 = Matched trades matching Criteria provided on requestYint
263SubscriptionRequestTypeUsed to subscribe / unsubscribe for trade capture reports.DLTF supported values: 0 = SnapshotNchar
748TotNumTradeReportsTotal number of trade reports returned. Will only be set when no trades were found for the requested criteria when it's value will be 0.Nint
749TradeRequestResultResult of Trade Request. DLTF Supported values: 0 = Successful (Default) 99 = OtherYint
750TradeRequestStatusStatus of Trade Request. DLTF Supported values: 0 = Accepted 2 = RejectedYint
58TextContains error message when Trade Capture Report Request is rejected.NString
StandardTrailerY

Tags

TagTag NameTypeDescription
1AccountStringThe DLTF Account ID. If not specified then the user's default account will be used.
6AvgPxPriceCalculated average price of all fills on this order.
7BeginSeqNoSeqNumMessage sequence number of first message in range to be resent
8BeginStringStringIdentifies beginning of new message and protocol version. ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted). Valid values: FIX.4.4
9BodyLengthLengthMessage length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN MESSAGE. (Always unencrypted)
10CheckSumStringThree byte, simple checksum (see Volume 2: “Checksum Calculation” for description). ALWAYS LAST FIELD IN MESSAGE; i.e. serves, with the trailing <SOH>, as the end-of-message delimiter. Always defined as three characters. (Always unencrypted)
11ClOrdIDStringThe client supplied identifier for the order. Must be unique for all currently working order. If a new order is received with the same ClOrdId as a currently working order then the new order will be rejected.
14CumQtyQtyTotal quantity (e.g. number of shares) filled.
16EndSeqNoSeqNumMessage sequence number of last message in range to be resent. If request is for a single message BeginSeqNo (7) = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = “0” (representing infinity).
17ExecIDStringUnique identifier of execution message as assigned by DLTF. Unique over all time.
18ExecInstMultipleStringValueInstructions for order handling on exchange trading floor. If more than one instruction is applicable to an order, this field can contain multiple instructions separated by space. Valid values: H = Reinstate on System Failure (Do not cancel on disconnect) Q = Cancel on System Failure (Cancel on disconnect)
22SecurityIDSourceStringIdentifies class or source of the SecurityID (48) value. Required if SecurityID is specified. DLTF Supported values are: 8 = Exchange Symbol
31LastPxPricePrice of this (last) fill.
32LastQtyQtyQuantity of contracts bought/sold on this fill.
34MsgSeqNumSeqNumInteger message sequence number.
35MsgTypeStringDefines message type ALWAYS THIRD FIELD IN MESSAGE. (Always unencrypted) Valid values: *** Note the use of lower case letters *** 0 = Heartbeat 1 = Test Request 2 = Resend Request 3 = Reject 4 = Sequence Reset 5 = Logout 8 = Execution Report 9 = Order Cancel Reject A = Logon D = Order – Single F = Order Cancel Request
36NewSeqNoSeqNumNew sequence number
37OrderIDStringUnique identifier for Order as assigned by DLTF. Unique over all time and orderbooks
38OrderQtyQtyQuantity of contracts ordered.
39OrdStatuscharIdentifies current status of order. DLTF supported values: 0 = New 1 = Partially filled 2 = Filled 4 = Canceled 8 = Rejected
40OrdTypecharOrder type. DLTF Supported values: 1 = Market 2 = Limit
41OrigClOrdIDStringClOrdID of the previous order. Used to identify the previous order in cancel requests.
43PossDupFlagBooleanIndicates possible retransmission of message with this sequence number. Valid values: Y = Possible duplicate N = Original transmission
44PricePricePrice per unit of quantity
45RefSeqNumSeqNumReference message sequence number
48SecurityIDStringDLTF Security identifier. Requires SecurityIDSource=8.
49SenderCompIDStringAssigned value used to identify firm sending message.
52SendingTimeUTCTimestampTime of message transmission (always expressed in UTC (Universal Time Coordinated, also known as “GMT”)
54SidecharSide of the order. Valid values: 1 = Buy 2 = Sell
55SymbolStringTicker symbol
56TargetCompIDStringAssigned value used to identify receiving firm.
58TextStringFree format text string (Note: this field does not have a specified maximum length)
59TimeInForcecharSpecifies how long the order remains in effect. Valid values: 1 = Good Till Cancel (GTC)
60TransactTimeUTCTimestampTime of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as “GMT”)
64SettlDateLocalMktDateSpecific date of trade settlement (SettlementDate) in YYYYMMDD format.
75TradeDateLocalMktDateIndicates date of trade referenced in this message in YYYYMMDD format. Absence of this field indicates current day (expressed in local time at place of trade).
89SignaturedataElectronic signature
93SignatureLengthLengthNumber of bytes in signature field.
95RawDataLengthLengthNumber of bytes in raw data field.
96RawDatadataUnformatted raw data, can include bitmaps, word processor documents, etc.
97PossResendBooleanIndicates that message may contain information that has been sent under another sequence number.Valid Values: Y=Possible resend N=Original transmission DLTF will never populate this tag with any value other than 'N' on messages sent by DLTF. DLTF will ignore this tag on any messages received by DLTF and the treat the message as having been sent with PossResend='N'.
98EncryptMethodintMethod of encryption. Valid values: 0 = None / other DLTF does not support encryption at the FIX layer. All messages are sent over an SSL encrypted connection. Supported values:
100ExDestinationExchangeExecution destination as defined by DLTF when order is entered.
102CxlRejReasonintCode to identify reason for cancel rejection. Valid values: 1 = Unknown order 2 = Broker / Exchange Option
103OrdRejReasonintCode to identify reason for order rejection. Valid values: 0 = Broker / Exchange option 1 = Unknown symbol 2 = Exchange closed 3 = Order exceeds limit 4 = Too late to enter 5 = Unknown Order 6 = Duplicate Order (e.g. duplicate ClOrdID ()) 7 = Duplicate of a verbally communicated order 8 = Stale Order 9 = Trade Along required 10 = Invalid nvestor ID 11 = Unsupported order characteristic 12 = Surveillence Option 13 = Incorrect quantity 14 = Incorrect allocated quantity 15 = Unknown account(s) 99 = Other Note: Values 3, 4, and 5 will be used when rejecting an order due to pre-allocation information errors.
108HeartBtIntintHeartbeat interval (seconds)
112TestReqIDStringIdentifier included in Test Request message to be returned in resulting Heartbeat
122OrigSendingTimeUTCTimestampOriginal time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as “GMT”) when transmitting orders as the result of a resend request.
123GapFillFlagBooleanIndicates that the Sequence Reset message is replacing administrative or application messages which will not be resent.Valid values: Y = Gap Fill message, MsgSeqNum field valid N = Sequence Reset, ignore MsgSeqNum
141ResetSeqNumFlagBooleanIndicates that the both sides of the FIX session should reset sequence numbers.Valid values: Y = Yes, reset sequence numbers N = No
146NoRelatedSymNumInGroupSpecifies the number of repeating symbols specified.
150ExecTypecharDescribes the specific ExecutionRpt (i.e. Pending Cancel) while OrdStatus (39) will always identify the current order status (i.e. Partially Filled) Valid values: 0 = New 4 = Canceled 8 = Rejected F = Trade (partial fill or fill) I = Order Status
151LeavesQtyQtyQuantity open for further execution. If the OrdStatus (39) is Canceled or Rejected (in which case the order is no longer active) then LeavesQty could be 0, otherwise LeavesQty = OrderQty (38) – CumQty (4).
263SubscriptionRequestTypecharSubscription Request Type DLTF supported values: 0 = Snapshot
354EncodedTextLenLengthUnused by DLTF. Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextdataUnused by DLTF. Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text field.
371RefTagIDintThe tag number of the FIX field being referenced.
372RefMsgTypeStringThe MsgType (35) of the FIX message being referenced.
373SessionRejectReasonintCode to identify reason for a session-level Reject message. Valid values: 0 = Invalid tag number 1 = Required tag missing 2 = Tag not defined for this message type 3 = Undefined Tag 4 = Tag specified without a value 5 = Value is incorrect (out of range) for this tag 6 = Incorrect data format for value 7 = Decryption problem 8 = Signature problem 9 = CompID problem 10 = SendingTime accuracy problem 11 = Invalid MsgType 12 = XML Validation error 13 = Tag appears more than once 14 = Tag specified out of required order 15 = Repeating group fields out of order 16 = Incorrect NumInGroup count for repeating group 17 = Non “data” value includes field delimiter (SOH character) 99 = Other
383MaxMessageSizeLengthMaximum number of bytes supported for a single message.
384NoMsgTypesNumInGroupNumber of MsgTypes (35) in repeating group.
385MsgDirectioncharSpecifies the direction of the messsage. Valid values: S = Send R = Receive
434CxlRejResponseTocharIdentifies the type of request that a Cancel Reject is in response to.DLTF Supported values: 1 = Order Cancel Request (F)
464TestMessageIndicatorBooleanNot supported by DLTF.
552NoSidesNumInGroupNumber of Side repeating group instances. Valid values: 1 = one side 2 = both sides
553UsernameStringDLTF username. This is required on the login message sent by the client
554PasswordStringDLTF Password or passphrase. This is required on the login message sent by the client
568TradeRequestIDStringTrade Capture Report Request ID. Must be unique string while a request is active
569TradeRequestTypeintType of Trade Capture Report. DLTF supported values: 1 = Matched trades matching Criteria provided on request
580NoDatesNumInGroupNumber of Date fields provided in date range
748TotNumTradeReportsintTotal number of trade reports returned. Will only be set when no trades were found for the requested criteria when it's value will be 0.
749TradeRequestResultintResult of Trade Request DLTF Supported values: 0 = Successful (Default) 99 = Other
750TradeRequestStatusintStatus of Trade Request.DLTF Supported values: 0 = Accepted 2 = Rejected
789NextExpectedMsgSeqNumSeqNumNot supported by DLTF.
790OrdStatusReqIDStringCan be used to uniquely identify a specific Order Status Request message.
912LastRptRequestedBooleanIndicates whether this message is that last report message in response to a request, such as Order Mass Status Request. Y = Last message N = Not last message
1101Custom tag: top of orderbook bid priceStringRepresent best bid price of orderbook on moment of trade execution
1102Custom tag: top of orderbook ask priceStringRepresent best ask price of orderbook on moment of trade execution
1103Custom tag: avg value between 1101 and 1102StringRepresent average value between best bid and best ask prices on moment of trade execution
1104Custom tag: total order feesStringRepresent value of cumulative order fees on moment of trade execution

Data Types

Data TypeDescription
Booleanchar field containing one of two values: 'Y' = True/Yes 'N' = False/No
charChar value, can include any alphanumeric character or punctuation except the delimiter. All char fields are case sensitive (i.e. l != L).
dataBinary (non-ASCII) data.
intSequence of digits without commas or decimals and optional sign character (ASCII characters - and 0 - 9). The sign character utilizes one byte (i.e. positive int is 99999 while negative int is -99999). Note that int values may contain leading zeros (e.g. 00023 = 23).
LengthRepresenting the length in bytes. Value must be positive.
NumInGroupValue that represents the number of repeating values in a group.
PriceValue representing a price. Note the number of decimal places may vary.
QtyValue capable of storing either a whole number (no decimal places) of shares (securities denominated in whole units) or a decimal value containing decimal places for non-share quantity asset classes (securities denominated in fractional units).
SeqNumRepresenting a message sequence number. Value must be positive.
StringAlpha-numeric free format strings; can include any character or punctuation except the delimiter. All char fields are case sensitive (i.e. dltf != DLTF).
UTCTimestampRepresenting Time/date combination represented in UTC (Universal Time Coordinated, also known as GMT ) only accepted in this format : YYYYMMDD-HH:MM:SS (whole seconds). For example 20120321-17:15:03.