developers:fixapi:reject [Documentation]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== REJECT [35=3] ======

The Reject message indicates FIX session rule violations.

===== Rejection Reasons =====
^ Code ^ Description ^
| 0 | Invalid tag number |
| 1 | Required tag missing |
| 2 | Tag not defined for message type |
| 3 | Undefined tag |
| 4 | Tag without value |
| 5 | Value out of range |
| 6 | Incorrect data format |
| 9 | CompID problem |
| 10 | SendingTime accuracy problem |
| 11 | Invalid MsgType |
| 13 | Duplicate tag |
| 14 | Tag out of order |
| 15 | Repeating group out of order |
| 16 | Incorrect NumInGroup count |
| 17 | Field delimiter in value |
| 18 | Invalid/missing trader |

===== Message Specification =====

**Message Direction:** T4 → Client

^ Tag ^ Field Name ^ Type ^ Req'd ^ Description ^
| | **Message Header** | | Y | MsgType = 3 |
| 45 | RefSeqNum | Int | Y | Sequence of rejected message |
| 371 | RefTagID | Int | O | Referenced tag number |
| 372 | RefMsgType | String | O | Referenced message type |
| 373 | SessionRejectReason | Int | O | Rejection code (see table) |
| 58 | Text | String | O | Rejection explanation |
| | **Message Trailer** | | Y | |

===== Sample Message =====

**SendingTime accuracy rejection:**
<code>
8=FIX.4.2|9=120|35=3|49=T4|56=T4Example|50=T4FIX|52=20120905-21:07:45.472|
45=12|372=F|373=10|58=Sending Time Accuracy problem|10=234|
</code>

===== Notes =====
  * Requires immediate corrective action
  * May lead to session termination
  * New session starts with sequence 1