> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/connectors/shop-floor-connectors/sopas/sopasendpoint.md).

# SOPAS Endpoint Properties

## `type` (string, enum, required)

The type of the identifier. It can be one of the following: event, method or variable.

This element must be one of the following enum values:

* `event`
* `method`
* `variable`

## `name` (string, required)

The name of the method to call. For example MIStartIn.

## `index` (string)

The index number of the method to call.

## `accessMode` (integer)

The access mode (user level) when writing to a variable in the device. The default access mode 0 (zero) is always active. Higher access modes such as 1 (Operator), 2 (Maintenance), 3 (Authorized Client), or 4 (Service) all require some password, which should be listed in the manufacturer's documentation. (The numbers 5 through 7 are internal values of the manufacturer.)

Default: `0`

Additional restrictions:

* Maximum: `7`

## `password` (string)

Only needed with an increased access mode (user level) parameter, when writing to a variable in the device.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/connectors/shop-floor-connectors/sopas/sopasendpoint.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.