> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsiam-api/logging-and-collection-service-management/models.md).

# Models

## The GetConnectedDevicesResponse object

```json
{"openapi":"3.0.1","info":{"title":"Cortex XSIAM Cloud Logging and Collection Service Management APIs","version":"1.0.0"},"components":{"schemas":{"GetConnectedDevicesResponse":{"type":"object","description":"The response envelope for the get connected devices operation.","properties":{"reply":{"type":"object","description":"The response payload containing the list of connected devices.","properties":{"devices":{"type":"array","description":"A list of NGFW devices currently connected to CLCS. Returns an empty array if no devices are connected.","items":{"$ref":"#/components/schemas/ConnectedDevice"}}},"required":["devices"]}},"required":["reply"]},"ConnectedDevice":{"type":"object","description":"Represents a single NGFW device connected to CLCS.","properties":{"device_id":{"type":"string","description":"The unique serial number of the NGFW device."},"csp_account_id":{"type":"integer","description":"The CSP (Cloud Service Provider) account ID that the device belongs to."},"region":{"type":"string","description":"The cloud region where the device is deployed."}},"required":["device_id","csp_account_id","region"]}}}}
```

## The ConnectedDevice object

```json
{"openapi":"3.0.1","info":{"title":"Cortex XSIAM Cloud Logging and Collection Service Management APIs","version":"1.0.0"},"components":{"schemas":{"ConnectedDevice":{"type":"object","description":"Represents a single NGFW device connected to CLCS.","properties":{"device_id":{"type":"string","description":"The unique serial number of the NGFW device."},"csp_account_id":{"type":"integer","description":"The CSP (Cloud Service Provider) account ID that the device belongs to."},"region":{"type":"string","description":"The cloud region where the device is deployed."}},"required":["device_id","csp_account_id","region"]}}}}
```

## The DisconnectDevicesRequest object

```json
{"openapi":"3.0.1","info":{"title":"Cortex XSIAM Cloud Logging and Collection Service Management APIs","version":"1.0.0"},"components":{"schemas":{"DisconnectDevicesRequest":{"type":"object","description":"The request body for disconnecting NGFW devices from CLCS.","properties":{"request_data":{"type":"object","description":"The parameters specifying which devices to disconnect.","properties":{"device_ids":{"type":"array","description":"A list of NGFW device serial numbers to disconnect. Must contain 1–1000 unique alphanumeric strings, each between 1 and 50 characters long.","minItems":1,"maxItems":1000,"items":{"type":"string","description":"An alphanumeric NGFW device serial number, between 1 and 50 characters.","minLength":1,"maxLength":50,"pattern":"^[a-zA-Z0-9]+$"}},"csp_account_id":{"type":"integer","description":"The CSP (Cloud Service Provider) account ID that the devices belong to. Must be a positive integer.","minimum":1},"region":{"type":"string","description":"The cloud region where the devices are deployed. Must be a non-empty string (not whitespace-only, not a numeric value).","minLength":1}},"required":["device_ids","csp_account_id","region"]}},"required":["request_data"]}}}}
```

## The DisconnectDevicesResponse object

```json
{"openapi":"3.0.1","info":{"title":"Cortex XSIAM Cloud Logging and Collection Service Management APIs","version":"1.0.0"},"components":{"schemas":{"DisconnectDevicesResponse":{"type":"object","description":"The response envelope for the disconnect devices operation.","properties":{"reply":{"type":"object","description":"The response payload containing the IDs of successfully disconnected devices.","properties":{"device_ids":{"type":"array","description":"The serial numbers of devices that were successfully disconnected. Device IDs from the request that were not found are silently omitted.","items":{"type":"string","description":"An alphanumeric NGFW device serial number."}}},"required":["device_ids"]}},"required":["reply"]}}}}
```

## The ErrorResponse object

```json
{"openapi":"3.0.1","info":{"title":"Cortex XSIAM Cloud Logging and Collection Service Management APIs","version":"1.0.0"},"components":{"schemas":{"ErrorResponse":{"type":"object","description":"A standard error response envelope returned when a request fails.","properties":{"reply":{"type":"object","description":"The error payload containing the status code, message, and additional detail.","properties":{"err_code":{"type":"integer","description":"The HTTP status code of the error."},"err_msg":{"type":"string","description":"A short description of the error."},"err_extra":{"type":"string","description":"Additional detail about the error, including remediation guidance where applicable."}},"required":["err_code","err_msg"]}},"required":["reply"]}}}}
```


---

# 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://cortex-docs.paloaltonetworks.com/xsiam-api/logging-and-collection-service-management/models.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.