Skip to main content

Overview

The Business Message Reject message (MsgType = "j") is sent by the gateway when an application-level message cannot be processed. It differs from a Session Reject because the message has valid FIX structure but fails for business reasons.

Field Layout

TagFieldDescriptionRequiredTypeValues
11ClOrdIDClient’s order identifier from the rejected messageYString
37OrderIdOrderId assigned by the gatewayYString
58TextHuman-readable rejection reasonNString
380BusinessRejectReasonRejection reason codeNString

Example Message

8=FIX.4.4|35=j|49=BUILDMARKETS|56=CLIENT1|11=ORD-20260212-010|37=BMKT-78470|380=5|58=Insufficient buying power for order|10=023|

Handling Business Rejects

  1. Examine Tag 58 (Text) for specific rejection details
  2. Review Tag 380 for coded rejection reasons
  3. The rejected order was not created — resolve the issue and resubmit
  4. Common causes: insufficient buying power, disabled options trading, invalid symbols, or unauthorized security types

REST Equivalent

The REST API responds with HTTP 4xx errors containing JSON error details when order validation fails.