ApplResponseError (FIX tag 1354)
ApplResponseError (tag 1354) is an int field defined in FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 3 defined values.
At a glance
- Tag
- 1354
- Name
- ApplResponseError
- Datatype
- int
- Dialects
- FIX 5.0 SP2
- Messages
- 1
- Valid values
- 3
What the specification says
Used to return an error code or text associated with a response to an Application Request.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1354
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 124 | |
| 35 | MsgType | BX | ApplicationMessageRequestAck |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1353 | ApplResponseID | EXAMPLE | |
| 1351 | NoApplIDs2 entries | 2 | repeating group |
| 1355 | RefApplID | EXAMPLE | |
| 1354 | ApplResponseError | 0 | Application does not exist |
| 1355 | RefApplID | EXAMPLE | |
| 1354 | ApplResponseError | 0 | Application does not exist |
| 10 | CheckSum | 138 |
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 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Valid values
A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.
| Value | Meaning | Symbolic name |
|---|---|---|
| 0 | Application does not exist | APPLICATION_DOES_NOT_EXIST |
| 1 | Messages requested are not available | MESSAGES_REQUESTED_ARE_NOT_AVAILABLE |
| 2 | User not authorized for application | USER_NOT_AUTHORIZED_FOR_APPLICATION |
Where tag 1354 appears
Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| ApplicationMessageRequestAck | BX | Optional | inside the ApplIDRequestAckGrp component |
Wire format
A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.
Read tag 1354 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const applResponseError = message.fields[1354]?.raw;// e.g. "0" — Application does not exist// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(1354) ?.enumValues?.find((e) => e.value === applResponseError) ?.description;Other int fields
- 1358LegPutOrCall
- 1349ApplTotalMessageCount
- 1348ApplResponseType
- 1347ApplReqType
- 1361TotNoFills
- 1343UnderlyingLegPutOrCall
- 1368TradSesEvent
- 1373MassActionType
- 1374MassActionScope
- 1375MassActionResponse
- 1376MassActionRejectReason
- 1377MultilegModel
- 1378MultilegPriceMethod
- 1323DerivativePutOrCall
- 1385ContingencyType
- 1386ListRejectReason
- 1320DerivativeListMethod
- 1388TrdRepPartyRole
- 1390TradePublishIndicator
- 1313DerivativeInstrAttribType
- 1400EncryptedPasswordMethod
- 1306PriceLimitType
- 1305SecondaryPriceLimitType
- 1304StrikeExerciseStyle
Decode 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-fix50sp2