> For the complete documentation index, see [llms.txt](https://docs.hookshothq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hookshothq.com/miscellaneous/demo-application.md).

# Demo Application

Hookshot maintains a "demo" application running at <https://demo.hookshothq.com>.

This basic "Todo List" application is meant as an example of a **user facing application** which uses Hookshot to allow it's users to configure and receive webhooks. It utilized the Hosted Management Pages feature of Hookshot.

At the moment, this demo application allows for public access to the Hookshot dashboard via shared credentials. You can use these credentials in order to explore the layout and functionality of the dashboard.

{% hint style="danger" %}
Any information entered into this demo application should be considered public information. Any configured webhooks should be considered public.
{% endhint %}


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hookshothq.com/miscellaneous/demo-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
