QST FIX Market Data API

https://qst.global/api_docs/qst_fix_market_data_api/
Admin
The QST FIX Market Data API provides access to market data using the Financial Information eXchange...
Tokens:35,721
Snippets:170
Trust Score:7.1
Update:11 months ago
Show doc for...
Tokens:
Raw
### FIX Market Data Snapshot Full Refresh Example

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_snapshot

An example of a FIX Market Data Snapshot Full Refresh (MsgType=W) message. This message is used to provide a complete snapshot of market data in response to a Market Data Request.

```fix
8=FIX.4.2|9=712|35=W|34=2|49=QSTFIXAPI|52=20200722-16:58:11.118252|56=ciumpy1|48=18531299|262=CL12.0001|268=17|269=1|270=325800|271=94|346=3|290=1|269=1|270=325825|271=99|346=1|290=2|269=1|270=325850|271=78|346=4|290=3|269=1|270=325875|271=104|346=1|290=4|269=1|270=325900|271=10|346=1|290=5|269=1|270=325925|271=110|346=1|290=6|269=1|270=32520000|271=50|346=1|290=7|269=0|270=325775|271=47|346=4|290=1|269=0|270=325725|271=98|346=4|290=2|269=0|270=325700|271=79|346=2|290=3|269=0|270=325625|271=1|346=1|290=4|269=0|270=325275|271=1313|346=2|290=5|269=0|270=325000|271=1|346=1|290=6|269=0|270=319725|271=10|346=1|290=7|269=0|270=319700|271=10|346=1|290=8|269=0|270=319675|271=20|346=2|290=9|269=0|270=319650|271=20|346=2|290=10|10=092|
```

--------------------------------

### Market Data Request - Multiple Security IDs Example

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Example of Market Data Request using multiple alternative security IDs to identify an instrument, demonstrating the use of security ID group repeating fields.

```APIDOC
## Market Data Request - Multiple Security IDs Example

### Example: Subscribe Using Alternative Security ID Representation

#### Request
```
8=FIX.4.2|9=173|35=V|34=2|49=user123|52=20210823-15:03:33.759|56=qst_qapi|60052=20210823-15:00:56.871|146=1|207=CME|454=1|455=ESZ21|456=99|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=020|
```

#### Field Breakdown
- **35**: Message Type = V (Market Data Request)
- **146**: NoRelatedSym = 1 (one instrument)
- **207**: SecurityExchange = CME
- **454**: NoSecurityAltID = 1 (one alternative security ID)
- **455**: SecurityAltID = ESZ21 (alternative symbol representation)
- **456**: SecurityAltIDSource = 99 (QST internal symbol)
- **262**: MarketDataRequestID = CL12.0001
- **263**: SubscriptionRequestType = 1 (subscribe for updates)
- **264**: MarketDataBookType = 0
- **265**: MDUpdateType = 1 (incremental)
- **267**: NoMDEntryTypes = 2 (request two data types)
- **269**: MDEntryType = 0 (Bid), 1 (Ask)
- **60052**: Timestamp = 20210823-15:00:56.871

#### Description
Subscribe to asks and bids for an instrument identified by alternative QST internal symbol representation (ESZ21). This example demonstrates using security alternative ID group for instrument identification.

#### Use Case
When the standard security ID is not available or when using alternative symbol representations from QST system.
```

--------------------------------

### FIX Security Status Request Message Examples

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/security_status_request

Examples of the Security Status Request (e) FIX message for different subscription types. These examples demonstrate how to request a snapshot, subscribe to updates, or unsubscribe from security status for a specific instrument. Note that the checksum (tag 10) may not be accurate in all provided examples.

```FIX
8=FIX.4.2|9=90|35=e|34=2|49=user123|52=20210823-15:45:51.592|56=qst_qapi|48=18531299|263=0|324=CL12.0001|10=077|
```

```FIX
8=FIX.4.2|9=90|35=e|34=2|49=user123|52=20210823-15:46:36.390|56=qst_qapi|48=18531299|263=1|324=CL12.0001|10=078|
```

```FIX
8=FIX.4.2|9=90|35=e|34=2|49=user123|52=20210823-15:46:54.011|56=qst_qapi|48=18531299|263=1|324=CL12.0001|10=068|
```

--------------------------------

### FIX Logon Request and Responses

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages/logon

Demonstrates the FIX message format for client logon requests and server responses. Includes examples of a successful logon and a failed logon, showing the message structure, sequence numbers, and error details.

```fix
8=FIX.4.2|9=115|35=A|34=1|49=user|52=20210823-14:39:14.717|56=MYFIXSERVER|96=password|98=0|108=30|141=Y|30001=host|30002=127.0.0.1|10=122|

```

```fix
8=FIX.4.2|9=81|35=A|34=1|49=qst_qapinr|52=20210908-11:47:46.891716|56=user123|98=0|108=30|141=Y|10=227|

```

```fix
8=FIX.4.2|9=106|35=5|34=1|49=qst_qapinr|52=20210908-11:52:18.876283|56=user123|58=Rejected Logon Attempt: Login failed: 1|10=014|

```

--------------------------------

### Example: Receiving Security Status Information (FIX Protocol)

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/security_status

This example demonstrates receiving security status information for a specific instrument using the FIX protocol. It includes standard FIX header and trailer components along with message-specific tags like SecurityID, SecurityStatusReqID, and SecurityTradingStatus.

```fix
8=FIX.4.2|9=96|35=f|34=22|49=QSTFIXAPI|52=20200722-15:33:15.853726|56=ciumpy1|48=18531299|324=CL12.0001|326=17|10=172|
```

--------------------------------

### Market Data Request - Single Security ID Example

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Examples of Market Data Request messages using a single security ID to identify instruments. Demonstrates different identification methods including internal ID and exchange ID.

```APIDOC
## Market Data Request - Single Security ID Examples

### Example 1: Subscribe Using Internal Instrument ID with IDSource

#### Request
```
8=FIX.4.2|9=132|35=V|34=2|49=user123|52=20210823-14:56:27.357|56=qst_qapi|146=1|48=18531299|22=96|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=207|
```

#### Field Breakdown
- **35**: Message Type = V (Market Data Request)
- **146**: NoRelatedSym = 1 (one instrument)
- **48**: SecurityID = 18531299 (internal instrument ID)
- **22**: IDSource = 96 (QST internal ID)
- **262**: MarketDataRequestID = CL12.0001
- **263**: SubscriptionRequestType = 1 (subscribe for updates)
- **264**: MarketDataBookType = 0
- **265**: MDUpdateType = 1 (incremental)
- **267**: NoMDEntryTypes = 2 (request two data types)
- **269**: MDEntryType = 0 (Bid), 1 (Ask)

#### Description
Subscribe to asks and bids for an instrument identified by instrument internal ID.

---

### Example 2: Subscribe Using Internal ID Without IDSource

#### Request
```
8=FIX.4.2|9=136|35=V|34=2|49=user123|52=20211104-10:16:59.304|56=qst_qapi|146=1|48=32111818|262=CL12.0001|263=1|264=0|265=1|267=3|269=0|269=1|269=B|10=182|
```

#### Field Breakdown
- **48**: SecurityID = 32111818
- **262**: MarketDataRequestID = CL12.0001
- **267**: NoMDEntryTypes = 3
- **269**: MDEntryType = 0 (Bid), 1 (Ask), B (Trade volume)
- **Note**: IDSource (tag 22) is omitted

#### Description
Subscribe to asks, bids, and trade volume for an instrument identified by internal ID without specifying IDSource.

---

### Example 3: Subscribe Using Exchange ID

#### Request
```
8=FIX.4.2|9=136|35=V|34=2|49=user123|52=20210823-14:57:23.588|56=qst_qapi|146=1|48=21558|207=CME|22=8|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=170|
```

#### Field Breakdown
- **48**: SecurityID = 21558
- **207**: SecurityExchange = CME
- **22**: IDSource = 8 (Exchange ID)
- **262**: MarketDataRequestID = CL12.0001
- **267**: NoMDEntryTypes = 2
- **269**: MDEntryType = 0 (Bid), 1 (Ask)

#### Description
Subscribe to asks and bids for an instrument identified by exchange ID (CME).
```

--------------------------------

### Request Market Data (FIX Protocol) - Instrument by Alternative Symbol

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Example FIX message to subscribe to market data (bids, asks) for an instrument identified by an alternative QST internal symbol. This method uses tags like `Symbol` (455) and `SymbolSfx` (456) along with `OpenCloseSfx` (454).

```fix
8=FIX.4.2|9=173|35=V|34=2|49=user123|52=20210823-15:03:33.759|56=qst_qapi|60052=20210823-15:00:56.871|146=1|207=CME|454=1|455=ESZ21|456=99|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=020|
```

--------------------------------

### Request Market Data (FIX Protocol) - Instrument by Exchange ID

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Example FIX message to subscribe to market data (bids, asks) for an instrument identified by its exchange ID and security ID. Requires specifying the `Exchange` (207) and `SecurityID` (48) tags.

```fix
8=FIX.4.2|9=136|35=V|34=2|49=user123|52=20210823-14:57:23.588|56=qst_qapi|146=1|48=21558|207=CME|22=8|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=170|
```

--------------------------------

### Security Definition (d) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/security_definition

This message is used to send contract information in response to a security definition request or as an asynchronous security definition. It originates from the QST FIX server and is sent to a FIX client. The message must start with a Standard Header (MsgType=d) and end with a Standard Trailer.

```APIDOC
## POST /marketdata/securitydefinition

### Description
Sends contract information in response to a security definition request or as an asynchronous security definition.

### Method
POST

### Endpoint
/marketdata/securitydefinition

### Parameters
#### Request Body
- **SecurityReqID** (String) - Required - Unique ID for this request. Populated with the value from the incoming Security Definition Request (c) message.
- **SecurityResponseID** (int) - Required - Unique ID for this Security Definition (d) message.
- **SecurityResponseType** (String) - Required - Type of security definition response. Supported values: `4` (List of securities), `5` (Reject proposal), `6` (Cannot match criteria).
- **UnderlyingSecurityID** (String) - Optional - Underlying security's SecurityID.
- **TotalNumSecurities** (int) - Required - Number of securities matching the filter criteria in the request.
- **ExchTickSize** (decimal) - Required - Size of one base tick for this security.
- **ExchPointValue** (decimal) - Optional - Size of one point for this security.
- **DeliveryTerm** (String) - Optional - Term of delivery for the instrument (supported for API V1.0). Supported values: `M` (Month), `D` (Day).
- **SecurityType** (String) - Required - Asset class of the instrument. Supported values: `FUT`, `MLEG`, `OPT`, `B`, `E`, `ED`, `I`, `FX`, `CFD`, `PHY`.
- **NoMdFeedTypes** (Int) - Optional - Number of repeating FeedType entries (supported for API V2.0).
  - **MDFeedType** (String) - Optional - Class of service for a data feed (supported for API V2.0). Supported values: `O` (Outright book depth), `I` (Implied book depth).
  - **MarketDepth** (int) - Optional - Depth of the book (supported for API V2.0). `0` indicates unlimited depth.
- **NoEvents** (NumInGroup) - Optional - Number of entries in the event types repeating group.
  - **EventType** (int) - Optional - Type of event. Supported values: `5` (Expiration date), `6` (Activation date).
  - **EventDate** (LOCALMKtdATE) - Optional - Date the event occurred.

### Request Example
```json
{
  "SecurityReqID": "req123",
  "SecurityResponseID": 1,
  "SecurityResponseType": "4",
  "TotalNumSecurities": 5,
  "ExchTickSize": 0.01,
  "SecurityType": "FUT",
  "NoMdFeedTypes": 1,
  "MDFeedType": "O",
  "MarketDepth": 10,
  "NoEvents": 1,
  "EventType": 5,
  "EventDate": "2023-12-31"
}
```

### Response
#### Success Response (200)
- **Status** (String) - Indicates the success or failure of the operation.
- **Message** (String) - Provides details about the response.

#### Response Example
```json
{
  "Status": "Success",
  "Message": "Security definition message processed successfully."
}
```
```

--------------------------------

### Logon Message (A)

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages

Handles the establishment of a FIX session. It includes details for successful logon, session parameters, and potential error codes for failed logons.

```APIDOC
## Logon (A) Message

### Description
Initiates and establishes a FIX session connection. This message allows clients to authenticate and configure session parameters.

### Message Direction
- Client to Server

### Supported Tags
- `8` (BeginString)
- `35` (MsgType)
- `98` (EncryptMethod)
- `108` (HeartBtInt)
- `141` (ResetSeqNumFlag)
- `48` (StandardTrailer)
- `554` (Username)
- `555` (Password)

### Message Notes
- The `ResetSeqNumFlag` (141) should be set to 'Y' to request sequence number reset.
- `Username` (554) and `Password` (555) are used for authentication.

### Logon Failed Error Codes
- `911` (Invalid Username or Password)
- `912` (Account Locked)
- `913` (Session Rejected)

### Example
```json
{
  "BeginString": "FIX.4.2",
  "MsgType": "A",
  "EncryptMethod": "0",
  "HeartBtInt": 30,
  "ResetSeqNumFlag": "Y",
  "Username": "user123",
  "Password": "password123"
}
```
```

--------------------------------

### Logon(A) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages/logon

Establishes a connection between a FIX client and the QST FIX server. This message is used for initiating or continuing a session.

```APIDOC
## Logon(A) Message

### Purpose
Used to establish a connection between a FIX client and QST FIX server.

### Message Direction
From QST FIX server to FIX client and from FIX client to QST FIX server

### Supported tags

Note
Each Logon message should start with Standard Header component (with the tag **35** (**MsgType**) = `A`) and end with the Standard Trailer.

#### Tag 96: RawData
- **Required**: Y
- **Data type**: data
- **Description**: Logon password. The value must match the logon password for the FIX session. QST FIX server does not include this tag in its responses.

#### Tag 98: EncryptMethod
- **Required**: Y
- **Data type**: int
- **Description**: Method of encryption. As QST FIX server does not support encrypted logons, you must set the value to `0` (None/Other).

#### Tag 108: HeartBtInt
- **Required**: Y
- **Data type**: int
- **Description**: Heartbeat interval in seconds. Maximum value is `14` seconds.

#### Tag 141: ResetSeqNumFlag
- **Required**: Y
- **Data type**: Boolean
- **Description**: Whether to reset the sequence numbers on both sides of the FIX session. Valid values include `Y` (default) and `N` (not supported).
  - If `Y`, Tag **34** (**MsgSeqNum**) must be `1`.

### Message Notes
The Logon (A) message is used by a FIX client to begin a new or continue an existing session with QST FIX server.
When logging in to a Security Definition FIX session, a FIX client must always set **141** = `Y` and **34** = `1`; otherwise, QST FIX server sends a Logout (5) message with the message: “MsgSeqNum must be set to 1 if ResetSeqNumFlag is set to Y” in tag **58** (**Text**).

#### Data Flow Example
1. FIX client initiates a socket connection.
2. FIX client sends a Logon (A) message to QST FIX server.
3. QST FIX server verifies tags **56** (TargetCompID) and **96** (RawData) against user setup.
4. If errors occur (e.g., tag mismatch, invalid credentials), QST FIX server sends a Logout (5) message and closes the connection.
5. Server examines Tag **141** (ResetSeqNumFlag):
   - If `N`: Compares Tag **34** (MsgSeqNum) with its current sequence number. Handles mismatches by sending Logout (5) or Resend Request (2).
   - If `Y`: Expects Tag **34** (MsgSeqNum) to be `1`. Handles mismatches by sending Logout (5) and closing the connection.
6. QST FIX server sends a Logon (A) message to the FIX client.

### Logon Failed Error Codes
When the Logon fails, you will receive a message in the format: `Login failed: ErrorCode`.

- **1**: Invalid username or password.
- **2**: Second factor missing (if 2FA is enabled).
- **5**: Too many failed login attempts.
- **1000**: Login failed for any other reason.
```

--------------------------------

### Market Data Request (V) Message Overview

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Complete overview of the Market Data Request message used to request market data from QST FIX server, including subscription management, response behavior, and server interaction patterns.

```APIDOC
## Market Data Request (V) Message

### Description
The Market Data Request (V) message is used by a FIX client to request market data information from QST FIX server API. You can request information such as top of book (Bid, Ask, session prices) and market depth data.

### Message Type
- **Message Type**: V (35=V)

### Server Response Behavior

QST FIX server responds to a Market Data Request message with a Market Data Snapshot (W) message. Response behavior depends on subscription type:

#### Subscription Request Type (Tag 263) = 0
- **Behavior**: Snapshot only
- **Description**: QST FIX server sends one Market Data Snapshot (W) message and no further updates
- **Use Case**: One-time market data request

#### Subscription Request Type (Tag 263) = 1
- **Behavior**: Continuous updates
- **Description**: QST FIX server updates market data according to MDUpdateType setting (tag 265)
  - If tag 265 = 0: QST FIX server sends Market Data Snapshot (W) messages
  - If tag 265 = 1: QST FIX server sends Market Data Incremental Refresh (X) messages
- **Use Case**: Real-time market data feed

#### Subscription Request Type (Tag 263) = 2
- **Behavior**: Stop updates
- **Description**: QST FIX server stops sending market data updates
- **Use Case**: Cancel existing subscription

### Error Handling
If QST FIX server cannot fulfill a request due to an invalid instrument, it sends a Market Data Request Reject (Y) message.

### Key Fields
- **Tag 262**: Market Data Request ID
- **Tag 263**: Subscription Request Type (0=snapshot, 1=subscribe, 2=unsubscribe)
- **Tag 264**: Market Data Book Type
- **Tag 265**: MD Update Type (0=full snapshot, 1=incremental)
- **Tag 267**: NoMDEntryTypes - Number of MDEntryType values
- **Tag 269**: MDEntryType - Types of market data requested
- **Tag 146**: NoRelatedSym - Number of instruments
```

--------------------------------

### Market Data Request Reject(Y) Message Example - FIX

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request_reject

An example of a Market Data Request Reject(Y) message in FIX protocol, indicating an unknown instrument. This message is used when the server cannot identify the instrument requested by the client or if mandatory fields are missing.

```FIX
8=FIX.4.2|9=139|35=Y|34=3|49=qst_qapi|52=20210823-15:06:54.915552|56=user123|58=Unknown instrument. Couldn\'t detect it. NoRelatedSym item: 2|262=CL12.0001|10=017|
```

--------------------------------

### Heartbeat(0) FIX Message Format Example

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages/heartbeat

Example of a complete Heartbeat(0) message transmitted between a FIX client and QST FIX server. The message includes the standard FIX header with MsgType=0, sequence number, sender/target identifiers, and timestamp. This demonstrates the expected format for heartbeat messages sent during regular communication intervals.

```text
8=FIX.4.2|9=61|35=0|34=15|49=user123|52=20210908-12:00:50.747|56=qst_qapinr|10=018|
```

--------------------------------

### Request Market Data (FIX Protocol) - Instrument by Internal ID

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_request

Example FIX messages to subscribe to market data (bids, asks, trade volume) for instruments identified by their internal ID. Supports different combinations of MDEntryTypes and ID sources.

```fix
8=FIX.4.2|9=132|35=V|34=2|49=user123|52=20210823-14:56:27.357|56=qst_qapi|146=1|48=18531299|22=96|262=CL12.0001|263=1|264=0|265=1|267=2|269=0|269=1|10=207|
```

```fix
8=FIX.4.2|9=136|35=V|34=2|49=user123|52=20211104-10:16:59.304|56=qst_qapi|146=1|48=32111818|262=CL12.0001|263=1|264=0|265=1|267=3|269=0|269=1|269=B|10=182||
```

--------------------------------

### Market Data Snapshot (W) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data

Provides a snapshot of market data, detailing message direction, supported tags, and notes.

```APIDOC
## Market Data Snapshot (W) Message

### Description
This message provides a snapshot of current market data. It details the message direction, supported tags, and specific notes related to the snapshot.

### Method
GET

### Endpoint
/marketdata/snapshot/{messageId}

### Parameters
#### Path Parameters
- **messageId** (string) - Required - The ID of the market data request message.

#### Query Parameters
None

#### Request Body
None

### Request Example
None

### Response
#### Success Response (200)
- **symbol** (string) - The trading symbol.
- **price** (number) - The current price of the asset.
- **volume** (integer) - The trading volume.

#### Response Example
```json
{
  "symbol": "AAPL",
  "price": 175.50,
  "volume": 1500000
}
```
```

--------------------------------

### Market Data Request (V) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data

Handles requests for market data, including message direction, supported tags, and notes.

```APIDOC
## Market Data Request (V) Message

### Description
This message is used to request market data. It includes details on message direction, supported tags, and any relevant notes.

### Method
POST

### Endpoint
/marketdata/request

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
- **tag** (string) - Required - Description of the tag
- **value** (string) - Optional - Value for the tag

### Request Example
```json
{
  "tag": "Symbol",
  "value": "AAPL"
}
```

### Response
#### Success Response (200)
- **messageId** (string) - Unique identifier for the market data message
- **status** (string) - Status of the market data request

#### Response Example
```json
{
  "messageId": "msg_12345",
  "status": "processed"
}
```
```

--------------------------------

### Test Request Message (1)

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages

Initiates a test to verify session connectivity. The counterparty must respond with a Heartbeat message containing the same `TestReqID`.

```APIDOC
## Test Request (1) Message

### Description
Initiates a test to ensure session connectivity. The recipient must respond with a Heartbeat message that includes the `TestReqID`.

### Message Direction
- Client to Server / Server to Client

### Supported Tags
- `8` (BeginString)
- `35` (MsgType)
- `112` (TestReqID)
- `10` (CheckSum)

### Message Notes
- The `TestReqID` (112) is a unique identifier for the test request.

### Example
```json
{
  "BeginString": "FIX.4.2",
  "MsgType": "1",
  "TestReqID": "TEST12345"
}
```
```

--------------------------------

### Component Instrument from FIX Client

Source: https://qst.global/api_docs/qst_fix_market_data_api/index

Defines how instrument information should be provided by the FIX client in requests.

```APIDOC
## Component Instrument from FIX Client

### Description
Specifies how FIX clients should represent instrument information in their requests.

### Specifying by Single Security ID
Instrument is identified using a single, unique security identifier.

### Specifying by Multiple Alternative Security IDs
Instrument can be identified using one of several alternative security identifiers.

### Specifying by Security Attributes
Instrument is identified by a set of descriptive attributes rather than a specific ID.
```

--------------------------------

### Logout(5) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/session_messages/logout

Used to terminate a connection between a FIX client and QST FIX server. This message can be sent in both directions: from QST FIX server to FIX client and from FIX client to QST FIX server. The message must start with a Standard Header component (with tag 35 set to value 5) and end with a Standard Trailer.

```APIDOC
## Logout(5) Message

### Description
Terminates a connection between a FIX client and QST FIX server. This message is bidirectional and can be sent by either party to close the connection.

### Message Direction
- From QST FIX server to FIX client
- From FIX client to QST FIX server

### Message Structure
- **MsgType (Tag 35)**: 5 (Logout)
- **Standard Header**: Required at start of message
- **Standard Trailer**: Required at end of message

### Supported Fields

#### Text - Tag 58
| Attribute | Value |
|-----------|-------|
| Tag Number | 58 |
| Field Name | Text |
| Required | No |
| Data Type | String |
| Description | Information to include with the message |

### Message Example
```
35=5|58=Connection terminated|93=0|89=|
```

### Notes
- The Logout message should always start with a Standard Header component containing tag 35 with value 5
- The message should always end with a Standard Trailer
- The Text field (tag 58) is optional and can be used to provide additional information about the logout reason
- This message is used to gracefully close FIX protocol connections
```

--------------------------------

### Market Data Snapshot Full Refresh (W) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data/market_data_snapshot

The Market Data Snapshot Full Refresh (W) message is used to respond to a Market Data Request, providing a full snapshot of the market data.

```APIDOC
## Market Data Snapshot Full Refresh (W) Message

### Description
The Market Data Snapshot Full Refresh (W) message is used by QST FIX server to respond to a Market Data Request (V) in the following cases:
  * One time, immediately after an incremental subscription before getting the initial incremental updates.
  * Tag 263 (SubscriptionRequestType) in the request is `0`, indicating the client wants a single market snapshot.
  * Tag 263 (SubscriptionRequestType) in the request is `1` and Tag 265 (MDUpdateType) is `0`, indicating the client subscribed to full market updates.

### Request Example
```
8=FIX.4.2|9=712|35=W|34=2|49=QSTFIXAPI|52=20200722-16:58:11.118252|56=ciumpy1|48=18531299|262=CL12.0001|268=17|269=1|270=325800|271=94|346=3|290=1|269=1|270=325825|271=99|346=1|290=2|269=1|270=325850|271=78|346=4|290=3|269=1|270=325875|271=104|346=1|290=4|269=1|270=325900|271=10|346=1|290=5|269=1|270=325925|271=110|346=1|290=6|269=1|270=32520000|271=50|346=1|290=7|269=0|270=325775|271=47|346=4|290=1|269=0|270=325725|271=98|346=4|290=2|269=0|270=325700|271=79|346=2|290=3|269=0|270=325625|271=1|346=1|290=4|269=0|270=325275|271=1313|346=2|290=5|269=0|270=325000|271=1|346=1|290=6|269=0|270=319725|271=10|346=1|290=7|269=0|270=319700|271=10|346=1|290=8|269=0|270=319675|271=20|346=2|290=9|269=0|270=319650|271=20|346=2|290=10|10=092|
```
```

--------------------------------

### Security Definition Request (c) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data

Allows requesting security definitions, including message direction, supported tags, and notes.

```APIDOC
## Security Definition Request (c) Message

### Description
This message is used to request definitions for a security. It includes details on message direction, supported tags, and any specific notes.

### Method
POST

### Endpoint
/securities/definition/request

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
- **securityId** (string) - Required - The identifier for the security.
- **idSource** (string) - Optional - The source of the security ID.

### Request Example
```json
{
  "securityId": "AAPL",
  "idSource": "RIC"
}
```

### Response
#### Success Response (200)
- **requestId** (string) - Unique identifier for the definition request.
- **status** (string) - Status of the request.

#### Response Example
```json
{
  "requestId": "req_abcde",
  "status": "pending"
}
```
```

--------------------------------

### Session Messages

Source: https://qst.global/api_docs/qst_fix_market_data_api/index

This section details the standard FIX session messages used for establishing and maintaining connections with the QST FIX server.

```APIDOC
## Session Messages

### Description
Covers standard FIX session messages including Logon, Logout, Heartbeat, and Test Request.

### Logon (A) Message
Establishes a connection between a FIX client and the QST FIX server.

### Logout (5) Message
Terminates an established FIX session.

### Heartbeat (0) Message
Sent periodically to ensure the session is active.

### Test Request (1) Message
Used to verify the responsiveness of the counterparty.
```

--------------------------------

### Market Data Incremental Refresh (X) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data

Delivers incremental updates to market data, including message direction, supported tags, and notes.

```APIDOC
## Market Data Incremental Refresh (X) Message

### Description
This message provides incremental updates to market data. It outlines the message direction, supported tags, and important notes regarding the refresh.

### Method
GET

### Endpoint
/marketdata/refresh/{messageId}

### Parameters
#### Path Parameters
- **messageId** (string) - Required - The ID of the market data request message.

#### Query Parameters
None

#### Request Body
None

### Request Example
None

### Response
#### Success Response (200)
- **updates** (array) - An array of market data updates.
  - **field** (string) - The market data field that was updated.
  - **value** (any) - The new value for the field.

#### Response Example
```json
{
  "updates": [
    {
      "field": "price",
      "value": 176.00
    },
    {
      "field": "volume",
      "value": 1550000
    }
  ]
}
```
```

--------------------------------

### Business Message Reject (j) Message

Source: https://qst.global/api_docs/qst_fix_market_data_api/market_data

Handles rejections for business messages, specifying message direction, supported tags, and notes.

```APIDOC
## Business Message Reject (j) Message

### Description
This message is used to reject a business message. It specifies the message direction, supported tags, and relevant notes for the rejection.

### Method
POST

### Endpoint
/messages/reject

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
- **messageId** (string) - Required - The ID of the rejected business message.
- **reason** (string) - Required - The reason for the rejection.

### Request Example
```json
{
  "messageId": "biz_msg_789",
  "reason": "Invalid message format"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the rejection was processed.

#### Response Example
```json
{
  "status": "rejected"
}
```
```

--------------------------------

### Component Instrument from QST FIX server response

Source: https://qst.global/api_docs/qst_fix_market_data_api/index

Details how the QST FIX server represents instrument information in its responses.

```APIDOC
## Component Instrument from QST FIX server response

### Description
Specifies how the QST FIX server represents instrument information in its responses, including supported tags.

### Supported Tags
Lists the specific FIX tags used by the server to describe instruments.
```
Tokens:
Raw