> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-webhooks/how-to-get-a-detailed-change-request-on-update-webhooks.md).
# How to get a detailed change request on update-webhooks
A guide on how to get a detailed change request on an update-webhook
## **Why use detailed change requests?**
Detailed change requests give you a clear view of exactly what was modified during an update. Instead of just knowing which items changed, you get the specific fields and values that were updated. This makes it easier to take targeted actions, reduce errors, and improve the accuracy of your integrations.
## Detailed change requests
To receive detailed change requests, you need to change the Data mode under Setup request from **“Ids only”** to **“Change set.”** Once selected, an example of the detailed change data will be shown to help you understand the format. For example, if you were to update an asset instead of just being shown the id of the asset that was updated, you will instead also be shown the attributes that were updated.
---
# 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.struct.com/tutorials/guides/how-to-use-webhooks/how-to-get-a-detailed-change-request-on-update-webhooks.md?ask=&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.
