API documentation

Business Reject (j)

Apart from malformed FIX messages, there may be combinations of FIX tags with values that do not make sense on a business level. For example, orders on instruments that are not supported. These messages will be rejected with a Business Reject (35=j) message.

Fields

TagNameReqDescription

Tag
Name
Header
ReqY
Description
Standard header, with 35=j.
Tag45
Name
RefSeqNum
ReqN
Description
The MsgSeqNum (34) of the referenced message.
Tag372
Name
RefMsgType
ReqY
Description
The MsgType (35) of the referenced message.
Tag380
Name
BusinessRejectReason
ReqY
Description
The number that represents the reason for the reject. Supported values: 0 = Other 1 = Unknown ID 2 = Unknown Security 3 = Unsupported Message Type 4 = Application not available 5 = Conditionally Required Field Missing 6 = Not authorized 7 = DeliverTo firm not available at this time 18 = Invalid price increment
Tag58
Name
Text
ReqN
Description
Message
Tag
Name
Trailer
ReqY
Description

YRequired — include this field in every message.

NOptional — may be omitted.

N*Conditionally required — optional unless noted in Description (look for (*)).

Example message

Session

8=FIX.4.4|9=82|35=j|49=YOUR_SENDER_COMP_ID|56=OBERMIND|34=1|52=20260610-12:00:00.000|372=D|380=1|10=168|

No paired server response is generated for this message type in the docs examples.

Pipe format uses | between fields for readability. On the wire, replace each | with ASCII SOH (0x01), or switch to SOH (wire) and copy directly into your FIX API session.

Lanza tu plataforma.

Empieza.