> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/apis/track-when-output-control-was-changed-via-api.md).

# Track when output control was changed via API

Query audit logs via user/audit/log/list to track output control changes, or create state change alerts and read notification history

## Question

Can we get the last updated time of output control through the API?

## Answer

Two options depending on what you need:

1. **Platform/API change history**

   Use `user/audit/log/list`.

   Filter by output control actions.
2. **Actual output state change**

   Create an output state change alert.

   Then read notifications via history endpoints.

Summary:

* Use audit logs to track platform/API actions for output control.
* Use events if you want to know when output state physically changed, regardless of how it was triggered.

## Links

* [Audit log list](/docs/navixy-api/user-api/resources/commons/user/audit/audit_log.md)
* [Output triggering (UI)](/docs/user/guide/events-and-notifications/inputs-and-outputs/output-triggering.md)
* [History user list](/docs/navixy-api/user-api/resources/commons/history/history-user.md#post-history-user-list)


---

# 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://navixy.com/docs/qna/apis/track-when-output-control-was-changed-via-api.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.