> For the complete documentation index, see [llms.txt](https://docs.sigrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigrex.io/getting-started/webhook.md). # Bot Webhook A bot **webhook** is a unique endpoint (URL) that can receive trading signals and trigger actions—such as executing trades on crypto exchanges or Web3 platforms like Uniswap. In Sigrex, users can easily create webhooks by filling out a few fields: *** ## 📝 Webhook Fields * **Name (optional):**\ You can give your webhook any name you like. If you leave it empty, the system will automatically generate a random, human-readable name (e.g., `silent-rain-9283`). * **Description:**\ Describe what the webhook is used for. You can include which trading symbols it listens to (e.g., `BTCUSDT`, `ETH`) and how frequently the signals are expected. This is especially helpful if you're planning to share the webhook with others. * **Key Protection:**\ Enabling this feature lets you protect your webhook with a custom key. Only signals that include a matching `"key": "your-secret-key"` field in their payload will be accepted. This helps ensure only trusted signals are processed. *** ## 🔗 After Webhook Creation Once the webhook is successfully created: * The system generates a unique UUID for the webhook. * You'll receive a webhook URL that you can copy and paste into tools like TradingView or connect it to your bot. * The webhook URL follows this format: `https://hook.sigrex.io/bot/` For example: `https://hook.sigrex.io/bot/72d7c761-8ee8-4fed-8400-1130ce689957` * Your webhook hash also works as an **email address** (e.g., `webhook-hash@sigrex.io`). Sigrex can detect if an email is a valid signal payload and, if so, trigger the connected trades. Non-signal emails (e.g., verification emails) will be forwarded to your registered email instead. > **Note:** Send the email in plain text format, not HTML. HTML-formatted emails may not be detected as a valid signal payload. *** ## ⚙️ Webhook Actions After creating a webhook, you can: * **Start / Pause** the webhook * **Delete** it if no longer needed * **Share** it with others (friends or teammates) {% hint style="warning" %} Shared webhooks keep the actual URL and hash private. Others only see the **name** and **description**, and can link it to their own SignalBots.. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sigrex.io/getting-started/webhook.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.