RefApplReqID (FIX tag 1433)

StringFIX 5.0 SP2

RefApplReqID (tag 1433) is a String field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 1433
Name: RefApplReqID
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 2

What the specification says

Used to reference a previously submitted ApplReqID (1346) from within a subsequent ApplicationMessageRequest(MsgType=BW)

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1433

ApplicationMessageRequest · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	143
35	MsgType	BW	ApplicationMessageRequest
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
1346	ApplReqID	EXAMPLE
1347	ApplReqType	0	Retransmission of application messages for the specified Applications
1351	NoApplIDs2 entries	2	repeating group
1355	RefApplID	EXAMPLE
1433	RefApplReqID	EXAMPLE
1355	RefApplID	EXAMPLE
1433	RefApplReqID	EXAMPLE
10	CheckSum	125

Edit and decode it yourself

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.

Open in the full decoder →

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.

Where tag 1433 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
ApplicationMessageRequest	BW	Optional	inside the ApplIDRequestGrp component
ApplicationMessageRequestAck	BX	Optional	inside the ApplIDRequestAckGrp component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1433 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1433];field?.name;   // "RefApplReqID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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

Try the decoder Source on GitHub