UserStatus (FIX tag 926)

intFIX 4.4FIX 5.0 SP2

UserStatus (tag 926) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 6 defined values.

At a glance

Tag: 926
Name: UserStatus
Datatype: int
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 1
Valid values: 6

What the specification says

Indicates the status of a user

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

A real message using tag 926

UserResponse · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	94
35	MsgType	BF	User Response
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
923	UserRequestID	EXAMPLE
553	Username	EXAMPLE
926	UserStatus	1	Logged In
10	CheckSum	233

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	Dialects
1	Logged In	LOGGED_IN	FIX 4.4, FIX 5.0 SP2
2	Not Logged In	NOT_LOGGED_IN	FIX 4.4, FIX 5.0 SP2
3	User Not Recognised	USER_NOT_RECOGNISED	FIX 4.4, FIX 5.0 SP2
4	Password Incorrect	PASSWORD_INCORRECT	FIX 4.4, FIX 5.0 SP2
5	Password Changed	PASSWORD_CHANGED	FIX 4.4, FIX 5.0 SP2
6	Other	OTHER	FIX 4.4, FIX 5.0 SP2
7	Forced user logout by Exchange	FORCED_USER_LOGOUT_BY_EXCHANGE	FIX 5.0 SP2
8	Session shutdown warning	SESSION_SHUTDOWN_WARNING	FIX 5.0 SP2

Where tag 926 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
UserNotification	CB	—	Required	directly on the message body
UserResponse	BF	Optional	Optional	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 926 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 userStatus = message.fields[926]?.raw;// e.g. "1" — Logged In// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(926)  ?.enumValues?.find((e) => e.value === userStatus)  ?.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