> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kraken.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Message Reject

> Business-level rejection before the trading engine

<div className="api-banner">
  <span className="api-protocol fix">FIX</span>
  <span className="api-detail">session: trading</span>
  <span className="api-tag">35=j</span>
</div>

Business-level rejection, used when a message is well formed but fails a business rule, either at the gateway or when the matching engine admits it. This is where unsupported order features, an invalid Account, unknown symbols and orders, a ClOrdID that is not increasing or is already in use, rate limit breaches, risk limits and requests that time out surface. BusinessRejectRefID echoes the ClOrdID of the rejected message and BusinessRejectReason gives the code, with the detail in Text.

**Direction:** Kraken → client

***

<ResponseField name="header" type="" required>35=`j`</ResponseField>

<ResponseField name="45 - RefSeqNum" type="SeqNum">
  MsgSeqNum of the message being rejected.
</ResponseField>

<ResponseField name="372 - RefMsgType" type="string" required>
  MsgType of the message being rejected.
</ResponseField>

<ResponseField name="379 - BusinessRejectRefID" type="string">
  ClOrdID of the message being rejected.

  <span className="field-attr">Required:</span> Conditional
</ResponseField>

<ResponseField name="380 - BusinessRejectReason" type="integer" required>
  Why the message was rejected.

  **Possible values:**

  * `0` : Other - used for nearly every business reject: unsupported order features, an invalid Account, a ClOrdID that is not increasing or already in use, rate limit breaches, risk limits and engine refusals. Also used when the lookup behind an OrderStatusRequest fails. Read Text (58).
  * `1` : Unknown id - an amend names an order the session does not hold. A cancel for an unknown order is answered with an OrderCancelReject (`35=9`, CxlRejReason `1`) where that is enabled.
  * `2` : Unknown instrument - Symbol or InstrumentID matches no tradable contract.
  * `101` : Unknown order - an OrderStatusRequest for an order that is finished or not in the cache.
  * `104` : Order too old - defined, but effectively never sent on US Perps: a finished order is answered with `101`.

  Values `3`, `4`, `5`, `6`, `8`, `100`, `102` and `103` are defined by the Unified FIX dictionary but are not sent on US Perps order entry: a rate limit breach, a reused ClOrdID and an engine refusal all arrive as `0`, with the cause in Text (58).
</ResponseField>

<Note>
  **Business rejects: venue differences**

  | | US Perps | Spot | Futures |
  | :- | :- | :- | :- |
  | Unknown order on a cancel | `35=9` with CxlRejReason `1` (where enabled) | `35=j`, `380=1` | `35=j`, `380=1` |
  | Unknown order on an amend | `35=j`, `380=1` | `35=j`, `380=1` | `35=j`, `380=1` |
  | Unknown order on a status request | `35=j`, `380=101` | `35=j`, `380=101` | Status requests are off |
</Note>

<ResponseField name="58 - Text" type="string">
  Free-text description: the cancellation reason, reject reason, or order status detail.

  **Format:** Free text set by Kraken; carries the reject or cancellation reason.
</ResponseField>

<ResponseField name="trailer" type="" required />