SecurityRequestResult (FIX tag 560)

intFIX 4.4

SecurityRequestResult (tag 560) is an int field defined in FIX 4.4. It appears in 2 message types and is required in 2 of them. It is an enumerated field with 6 defined values.

At a glance

Tag: 560
Name: SecurityRequestResult
Datatype: int
Dialects: FIX 4.4
Messages: 2
Valid values: 6

What the specification says

The results returned to a Security Request message

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

A real message using tag 560

DerivativeSecurityList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	94
35	MsgType	AA	Derivative Security List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
320	SecurityReqID	EXAMPLE
322	SecurityResponseID	EXAMPLE
560	SecurityRequestResult	0	Valid request
10	CheckSum	205

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.

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	Valid request	VALID_REQUEST
1	Invalid or unsupported request	INVALID_OR_UNSUPPORTED_REQUEST
2	No instruments found that match selection criteria	NO_INSTRUMENTS_FOUND_THAT_MATCH_SELECTION_CRITERIA
3	Not authorized to retrieve instrument data	NOT_AUTHORIZED_TO_RETRIEVE_INSTRUMENT_DATA
4	Instrument data temporarily unavailable	INSTRUMENT_DATA_TEMPORARILY_UNAVAILABLE
5	Request for instrument data not supported	REQUEST_FOR_INSTRUMENT_DATA_NOT_SUPPORTED

Where tag 560 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
DerivativeSecurityList	AA	Required	directly on the message body
SecurityList	y	Required	directly on the message body

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 560 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 securityRequestResult = message.fields[560]?.raw;// e.g. "0" — Valid request// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(560)  ?.enumValues?.find((e) => e.value === securityRequestResult)  ?.description;

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