> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalnotificationgetvalue.md).

# OpalNotificationGetValue

<table data-header-hidden><thead><tr><th width="199.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Utilities</td></tr><tr><td><strong>Description</strong></td><td>Returns the values of the parameter(s) or signal(s) that have been modified when an event OP_PARAMETER_UPDATE or OP_SIGNAL_CHANGE is notified. This function should be called from within the callback function registered for the events listed above. It allows more information about the notification to be gathered upon the reception of such events.<br>This function allocates the memory for the <em>valueList</em> pointer. User should call OpalFreeMemory to desallocate this pointer when the variable is no longer in use.</td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalNotificationGetValue</strong>(OP_NOTIFICATION returnedNotification,int *numberOfElements, int **valueList);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>returnedNotification:</strong> Notification structure that was previously returned withthe OP_PARAMATER_UPDATE or OP_SIGNAL_CHANGEevent.</li></ul></td></tr><tr><td><strong>Output</strong></td><td><ul><li><strong>numberOfElements:</strong> Number of parameter(s) or signal(s) that was modified.</li><li><strong>valueList:</strong> List of the element IDs. If this parameter is NULL, the function only returns the number of elements.</li></ul></td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Success.</li><li><strong>EINVAL:</strong> Invalid notification structure.</li><li><strong>ENOMEM:</strong> Unable to allocate memory for the returned pointer.</li><li><strong>EIO:</strong> Invalid or incomplete data received from the model.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>See the API <strong>parameter1</strong> or <strong>signal1</strong> examples.</td></tr><tr><td><strong>Related items</strong></td><td>OP_EVENTS, OP_NOTIFICATION, OpalNotificationGetID, OpalNotificationGetPathName, OpalSetNotificationCallback</td></tr></tbody></table>


---

# 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://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/rt-lab-api/c-rt-lab-api-reference/functions-reference/opalnotificationgetvalue.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.
