---
title: "ServerResponse"
slug: "api/session/types/serverresponse"
sidebar:
  order: 135
---

<a id="ref-f18611a9a34a"></a>
<a id="ref-0bdfa87043cf"></a>
<a id="ref-3ef0a7abf48e"></a>

## Synopsis

```text
final struct ServerResponse{
    string origin;
    string messageId;
    StringPair[]      data;
    SendMessageStatus statusCode;
    string[]          errorDetail;
    string targetErrorCode
}
```

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

See also: [`SendMessageStatus`](/pCon/configuratorOnline/specs/api/session/types/sendmessagestatus#ref-e5f4d00086c9)

**`origin`**

Identifies the origin of the response. Same rules as for [ClientMessage](/pCon/configuratorOnline/specs/api/session/types/clientmessage).target, but the substring following plugin: is always non-empty.

**`messageId`**

Identifies the message. It is always equal to the messageId of the corresponding [ClientMessage](/pCon/configuratorOnline/specs/api/session/types/clientmessage).

**`data`**

Is the payload of the response, a possibly empty list of key/value pairs. Keys must adhere to the rules for NCName. data is always empty if statusCode is not OK.

**`statusCode`**

Is used to signal and identify error during message delivery.

**`errorDetail`**

Is used to provide additional information for some kinds of errors.
