Order Entry

Errors

Error Responses

When a message is received but cannot be properly processed due to some rule violation (like invalid field values or attributes), we will return back

a Reject <3>, or
an Execution Report <8> with an OrdStatus <39> field with a value of 8 = Rejected and an ExecType <150> field with a value of 8 = Rejected, or
a Business Message Reject <j>

Where possible, there will be an error message in Text <58> explaining the Rejection. Here is a list of some common error messages and reasons for Rejection.

Error Messages

Message Type	Error Message	Reason
Reject `<3>`	Value is incorrect (out of range) for this tag	Here are some reasons for why a field value may be invalid: • An order submitted on behalf of another party (identified by the OnBehalfOfCompID `<115>` field) is submitted through a channel that does not offer Third Party Support. • An attempt was made to trade on behalf of someone without permission • Order's TimeInForce `<59>` was invalid • Order quantity violates market minimums or increments for Symbol - see Supported Symbols • Incompatible fields, such as a response to an IOI which also includes an ExecInst `<18>`
Reject `<3>`	Tag not defined for this message type (TAG)	Message contains an extra unsupported FIX tag.
Reject `<3>`	Invalid tag value
Reject `<3>`	System Error: Message rate exceeded allocated throttle	Throttle exceeded
Execution Report `<8>` (Rejected)	InvalidPrice	The message specified a price that was too low or had the incorrect precision.
Execution Report `<8>` (Rejected)	Unsupported Symbol value 'ABCDEF'	An invalid Symbol was provided (ex: 'ABCDEFGH' instead of 'BTCUSD' in Symbol `<55>`)
Execution Report `<8>` (Rejected)	StopPx is required for OrdType: 4	New Stop Limit orders require a valid stop price in StopPx `<99>`.
Execution Report `<8>` (Rejected)	Price must be within 50% of StopPx for OrdType: 4	New Stop Limit orders require the Limit Price `<44>` be within 50% of the StopPx `<99>`.
Execution Report `<8>` (Rejected)	Stop limit orders only support standard order behavior	If provided, `1 = Good Till Cancel (GTC)` is the only TimeInForce `<59>` value allowed in conjunction with stop limit orders. All other values will trigger this rejection.
Business Message Reject `<j>`	Unsupported message type	Used to Reject a FIX message which is not unsupported by this specific FIX API, e.g. a Market Data Request `<V>` received on a FIX Order Entry Channel.
Business Message Reject `<j>`	Conditionally Required Field Missing (TAG)	A conditionally required field, identified by its tag, is missing. (ex: OrderQty `<38>` is missing)
Business Message Reject `<j>`	System Error: Application not available	Backend system not available

Introduction Third Party Support