EndSeqNo (FIX tag 16)
EndSeqNo (tag 16) is a SeqNum field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type and is required in 1 of them.
At a glance
- Tag
- 16
- Name
- EndSeqNo
- Datatype
- SeqNum (int)
- Dialects
- FIX 4.4 and FIX 4.2
- Messages
- 1
What the specification says
FIX 4.4
Message sequence number of last message in range to be resent. If request is for a single message BeginSeqNo (7) = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = "0" (representing infinity).
FIX 4.2
Message sequence number of last message in range to be resent. If request is for a single message BeginSeqNo = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = "0" (representing infinity).
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 16
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 72 | |
| 35 | MsgType | 2 | Resend Request |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 7 | BeginSeqNo | 1 | |
| 16 | EndSeqNo | 1 | |
| 10 | CheckSum | 044 |
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.
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 16 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 4.2 | Where in the message |
|---|---|---|---|---|
| ResendRequest | 2 | Required | Required | directly on the message body |
Wire format
A positive sequence number. Session-level, and monotonic within a session. @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 16 in TypeScript
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[16];field?.name; // "EndSeqNo"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther SeqNum fields
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