# Supported Message Type

### Administrative Messages <a href="#administrative-messages" id="administrative-messages"></a>

The following Administrative message types are supported under `MsgType (35)`:

* Logon (35=A)
* HeartBeat (35=0)
* TestRequest (35=1)
* ResendRequest (35=2)
* Reject (35=3)
* SequenceReset (35=4)
* Logout (35=5)

### Application Messages <a href="#application-messages" id="application-messages"></a>

Once you are connected to the National Digital Asset Exchange (NDAX) FIX Straight Through Processing (STP) Gateway, the TradeCaptureReport serves as the FIX message that contains the trade details for the NDAX Settlement Service to process and execute. The TradeCaptureReport includes a number of tags and fields that describe the data objects necessary to report trades on behalf of the counterparties involved in the trade. These tags and fields specify important information about the trade, such as the type of trade, the assets involved, the prices and quantities, and the parties involved. By sending the TradeCaptureReport to the NDAX Settlement Service through the FIX STP Gateway, you can facilitate the settlement of trades and ensure that the appropriate assets are transferred to the correct parties. The TradeCaptureReport is an essential component of the settlement process and is used to communicate trade information between the NDAX platform and the counterparties involved in the trade.

* TradeCaptureReport (35=AE)
* TradeCaptureReportAck (35=AR)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ndax.in/v3/fix/supported-message-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.