> 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-view-webhook-request-history.md). # How to view webhook request history A guide on how to view request history for a webhook ## Viewing request history In order to view the request history for a webhook, Right-click on the webhook you created and select "View Webhook Requests." This action will take you to a page displaying all requests triggered by the webhook, along with response codes indicating the status of each request.

## Example of webhook request history In the image below, the webhook "TestWebhook" has made three requests based on events where variants were updated. Each request has a unique UID, and all three were successful, as indicated by the **200** response code received.

Furthermore, you can also inspect each request by clicking on them to view a more detailed report for each request. Here you will be able to see everything from the request headers to the response headers and the request body.

--- # 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-view-webhook-request-history.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.