---
title: "ClientMessage"
slug: "api/session/types/clientmessage"
sidebar:
  order: 109
---

<a id="ref-7f622e430491"></a>
<a id="ref-7c964af74cd3"></a>
<a id="ref-15a14a204c23"></a>
<a id="ref-b69452ef3032"></a>

## Synopsis

```text
final struct ClientMessage{
    string target;
    string messageId;
    StringPair[] data;
}
```

See also: [`StringPair`](/pCon/configuratorOnline/specs/api/session/types/stringpair#ref-1952c029f1cd)

**`target`**

Identifies the target of the message. It consists of a prefix and a prefix-specific string. As of now, the prefix must be plugin: and the substring following the prefix must be empty or equal to a plugin ID.

**`messageId`**

identifies the message. It must adhere to the rules for QName as specified in Namespaces in XML 1.1, Second Edition). For plugin-specific messages it should be just a NCName.

**`data`**

Is the payload of the message, a possibly empty list of key/value pairs. Keys must adhere to the rules for NCName.
