FIX Protocol Message 35=BE: User Request
Logs a user on or off, changes a user password, or requests a user status. It works at user level, separate from the session Logon.
- MsgType (tag 35)
- BE
- FIX name
- UserRequest
- Category
- Application
- FIX versions
- FIX 4.4 to 5.0 SP2
User Request in each FIX version
The full field layout as defined in a specific version.
Required fields
Body fields that every User Request message must carry in FIX 4.4, in addition to the standard header and trailer.
- 923UserRequestID
- 924UserRequestType
- 553Username
Field layout
All body fields in the order of the FIX 4.4 definition, with components and repeating groups indented. A field inside an optional component or group is required only when that component or group is present. Later FIX 5.0 service packs add more fields to this message.
| Tag | Field | Required |
|---|---|---|
| 923 | UserRequestID | Required |
| 924 | UserRequestType | Required |
| 553 | Username | Required |
| 554 | Password | Optional |
| 925 | NewPassword | Optional |
| 95 | RawDataLength | Optional |
| 96 | RawData | Optional |
Standard header and trailer
Every FIX message starts with the standard header, whose required fields are BeginString (8), BodyLength (9), MsgType (35), SenderCompID (49), TargetCompID (56), MsgSeqNum (34) and SendingTime (52), and ends with the trailer field CheckSum (10).
Decode a User Request messageAll FIX message types · All FIX tags
Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.