5 Sub-appendix 4.3, Decision_act (EU) 2018/1926

In force

1.1.

The central hub shall provide both synchronous and asynchronous interfaces for the exchange of messages. Parties may choose the most suitable technology to interface with their own applications.

1.2.

All messages exchanged between the central hub and the national systems must be UTF-8 encoded.

1.3.

National systems shall be capable of receiving and processing messages containing Greek or Cyrillic characters.

2.1.

The general structure of XML messages shall follow the format defined by the XSD schemas installed in the central hub.

2.2.

The central hub and the national systems shall transmit and receive messages that conform to the message XSD schema.

2.3.

National systems shall be capable of sending, receiving and processing all messages corresponding to any of the functionalities set out in Sub-appendix 4.2.

2.4.

The XML messages shall include at least the minimum requirements laid down in Table 2.

Common Header | Mandatory

Version | The official version of the XML specifications will be specified through the namespace defined in the message XSD and in the version attribute of the Header element of any XML message. The version number (‘n.m’) will be defined as fixed value in every release of the XML Schema Definition file (xsd). | Yes

Test Identifier | Optional id for testing. The originator of the test will populate the id and all participants in the workflow will forward/return the same id. In production it should be ignored and will not be used if it is supplied. | No

Technical Identifier | A UUID uniquely identifying each individual message. The sender generates a UUID and populates this attribute. This data is not used in any business capacity. | Yes

Workflow Identifier | The workflow id is a UUID and should be generated by the requesting party. This id is then used in all messages to correlate the workflow. | Yes

Sent At | The date and time (UTC) that the message was sent. | Yes

Timeout | This is an optional date and time (in UTC format) attribute. This value will be set only by the central hub for forwarded requests. This will inform the responding party of the time when the request will be timed out. This value is not required in MS2TCN_<x>_Req and all response messages. It is optional so that the same header definition can be used for all message types regardless of whether or not the timeoutValue attribute is required. | No

From | The ISO 3166-1 Alpha 2 code of the party sending the message or ‘EU’. | Yes

To | The ISO 3166-1 Alpha 2 code of the party to which the message is being sent or ‘EU’. | Yes