> For the complete documentation index, see [llms.txt](https://docs.libum.io/nexum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libum.io/nexum/symxchange/device-information.md).

# Device Information

{% hint style="info" %}
**Symitar eDocs References:** [Instance Device Mapping](https://learnmore.symitar.com/edocs/#xml/SymXchange/SymXchangeDeviceCnfgInstnc_R.html), [SymXchange Device Control](https://learnmore.symitar.com/edocs/#xml/SymXchange/SymXchangeDeviceControl_R.html)
{% endhint %}

NexumAPI automatically includes the common <mark style="color:purple;">`DeviceInformation`</mark> object with each request payload as set in the configuration. This object is used by SymXchange to direct traffic to different clients on a single instance.

These values are set in the WebConsole and point to client configurations which are set in the SymXchange Parameters found in Parameter Manager.

### Definitions

* <mark style="color:purple;">`DeviceType`</mark> - the device type configured for the SymXchange instance
* <mark style="color:purple;">`DeviceNumber`</mark> - the identifier assigned to the instance device

## CU Build device mappings

The CU Build NexumAPI endpoints use a separate device mapping for each available Sym:

| Sym   | `DeviceType` | `DeviceNumber` |
| ----- | ------------ | -------------- |
| `777` | `LIBUM777`   | `20777`        |
| `888` | `LIBUM888`   | `20888`        |

For example, requests to Sym `777` use the following device information:

```json
{
  "DeviceInformation": {
    "DeviceType": "LIBUM777",
    "DeviceNumber": "20777"
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.libum.io/nexum/symxchange/device-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.