Message Structure
Each DAXP message is composed of four sections:
|
Each section is built using a series of tag=value pairs.
0. PREAMBLE
Preamble is the first line of every DAXP message that defines its global parameters — such as protocol version, tag format, encoding, and context — telling the receiver how to interpret the rest of the message.
Used tags:
| tag | Meaning | Description |
| DAXP | Protocol identifier | Declares the message belongs to the DAXP protocol, version 1. |
| TF | Tag Format | Defines how tag identifiers are represented — DEC for decimal (e.g., 4000), or HEX for hexadecimal (0x0FA0). |
| E | Encoding | Defines character encoding for values — supports ASCII, UTF8, or possibly UTF16 in the future. |
| \n | Terminator | Indicates end of preamble / start of body. The following lines contain the actual tag=value data. |
Example
|
DAXP=1|TF=DEC|E=UTF8\n |
1. HEAD
The header section contains metadata that identifies the message:
| 9 | DX_MSG_TYPE | MsgType | String | Message type |
| 15 | DX_TOKEN | Token | String | Token - used in asynchronous communication |
| 16 | DX_TIMESTAMP | MsgTimestamp | Timestamp | Message timestamp |
- Example
|
9=UA|15=xs12sewdffd24 |16=20251006-10:15:23.456| |
2. BODY
The main section contains business data and control data.
They may be defined by the application (e.g. microservice or GUI), nested, organized in lists, arrays, or repeating structures.
The BODY can also contain fixed-position fields to optimize message size in high-performance environments .
Example:
|
2001=10342|2002=AnyName|2003=AnySurname|2010=Warszawa|2011= |
The meaning of tags of their types has been previously provided in the form of a dictionary
2001 - Id customer;
2002 - Surename
2010 - city of residence
2011 - email
2073 - telephone
3. TRAILER
The final section serves a control purpose, containing a checksum (CRC or other algorithm)
to verify the integrity of the entire message.
| 99 | DX_CHECKSUM | Checksum | Integer |
Example :
|
99=238| |