ResponseDestination (FIX tag 726)

StringFIX 4.4FIX 5.0 SP2

ResponseDestination (tag 726) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 7 message types, always optionally.

At a glance

Tag: 726
Name: ResponseDestination
Datatype: String
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 7

What the specification says

FIX 4.4

URI (Uniform Resource Identifier) for details) or other pre-arranged value. Used in conjunction with ResponseTransportType (725) value of Out-of-Band to identify the out-of-band destination. See "Appendix 6-B FIX Fields Based Upon Other Standards"

FIX 5.0 SP2

URI (Uniform Resource Identifier) for details or other pre-arranged value. Used in conjunction with ResponseTransportType (725) value of Out-of-Band to identify the out-of-band destination. See Appendix 6-B FIX Fields Based Upon Other Standards

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

A real message using tag 726

TradeCaptureReportRequest · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	94
35	MsgType	AD	Trade Capture Report Request
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
568	TradeRequestID	EXAMPLE
569	TradeRequestType	0	All trades
726	ResponseDestination	EXAMPLE
10	CheckSum	239

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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 726 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	FIX 4.4	FIX 5.0 SP2	Where in the message
CollateralInquiry	BB	Optional	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	Optional	directly on the message body
RequestForPositions	AN	Optional	Optional	directly on the message body
RequestForPositionsAck	AO	Optional	Optional	directly on the message body
TradeCaptureReportAck	AR	Optional	Optional	directly on the message body
TradeCaptureReportRequest	AD	Optional	Optional	directly on the message body
TradeCaptureReportRequestAck	AQ	Optional	Optional	directly on the message body

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 726 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[726];field?.name;   // "ResponseDestination"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-fix44

Try the decoder Source on GitHub