Skip to content
FIXtags

FIX TAG 725

ResponseTransportType

intAdded FIX.4.4

Definition

Identifies how the response to the request should be transmitted. Details specified via ResponseDestination (726).

Compare versions

Differences between the selected source snapshots, including wording and errata; not a migration guide.

FIX 4.4 FIX 5.0 SP2

Definition text changed

FIX 4.4

Identifies how the response to the request should be transmitted.

FIX 5.0 SP2

Identifies how the response to the request should be transmitted. Details specified via ResponseDestination (726).

Value text or deprecation changed 2

ValueFIX 4.4FIX 5.0 SP2
0Inband: transport the request was sent over (Default)Inband - transport the request was sent over (default)
1Out-of-Band: pre-arranged out of band delivery mechanism (i.e. FTP, HTTP, NDM, etc) between counterparties. Details specified via ResponseDestination (726).Out of Band - pre-arranged out-of-band delivery mechanizm (i.e. FTP, HTTP, NDM, etc.) between counterparties. Details specified via ResponseDestination (726).

Values 2

ValueMeaning
0

Inband - transport the request was sent over (default)

1

Out of Band - pre-arranged out-of-band delivery mechanizm (i.e. FTP, HTTP, NDM, etc.) between counterparties. Details specified via ResponseDestination (726).

About the int data type

Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.

Used in messages 7

Includes nested components and repeating groups. Open a location to see its surrounding requirements.