SecurityStatusRequest (MsgType e)
SecurityStatusRequest is the FIX message with MsgType e, defined in FIX 4.4 and FIX 4.2. It is an application-level message: it carries a business event rather than managing the session. Its body has 11 top-level members once the standard header and trailer are counted.
e is SecurityStatusRequest, but E is a different message entirely — NewOrderList. Twenty-three FIX message types differ from another only by letter case.A real SecurityStatusRequest
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 81 | |
| 35 | MsgType | e | Security Status Request |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 324 | SecurityStatusReqID | EXAMPLE | |
| 263 | SubscriptionRequestType | 0 | Snapshot |
| 10 | CheckSum | 207 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Message body — FIX 4.4
Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.
- —Standard Message HeadercomponentRequired
- 324SecurityStatusReqIDRequired
- —InstrumentcomponentRequired
- —InstrumentExtensioncomponentOptional
- —UndInstrmtGrpcomponentOptional
- —InstrmtLegGrpcomponentOptional
- 15CurrencyOptional
- 263SubscriptionRequestTypeRequired
- 336TradingSessionIDOptional
- 625TradingSessionSubIDOptional
- —Standard Message TrailercomponentRequired
Message body — FIX 4.2
Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.
- —Standard Message HeadercomponentRequired
- 324SecurityStatusReqIDRequired
- 55SymbolRequired
- 65SymbolSfxOptional
- 48SecurityIDOptional
- 22SecurityIDSourceOptional
- 167SecurityTypeOptional
- 200MaturityMonthYearOptional
- 205MaturityDayOptional
- 201PutOrCallOptional
- 202StrikePriceOptional
- 206OptAttributeOptional
- 231ContractMultiplierOptional
- 223CouponRateOptional
- 207SecurityExchangeOptional
- 106IssuerOptional
- 348EncodedIssuerLenOptional
- 349EncodedIssuerOptional
- 107SecurityDescOptional
- 350EncodedSecurityDescLenOptional
- 351EncodedSecurityDescOptional
- 15CurrencyOptional
- 263SubscriptionRequestTypeRequired
- 336TradingSessionIDOptional
- —Standard Message TrailercomponentRequired
What changed between the dialects
Present in FIX 4.4 only (5)
Instrument, InstrumentExtension, UndInstrmtGrp, InstrmtLegGrp, tag 625
Present in FIX 4.2 only (19)
tag 55, tag 65, tag 48, tag 22, tag 167, tag 200, tag 205, tag 201, tag 202, tag 206, tag 231, tag 223, tag 207, tag 106, tag 348, tag 349, tag 107, tag 350, tag 351
Handle SecurityStatusRequest in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);if (message.msgType === "e") { message.name; // "SecurityStatusRequest" // fields are keyed by tag; repeating groups live on message.groups}// Problems come back as data, never as exceptions:issues; // FixIssue[]fix.validate(message); // dictionary-level problemsDecode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix44