> 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/reaction/data-webhook.md).

# Data Webhook

A Data Webhook allows external systems to send data into Sigrex. Incoming data can then be processed by Reactions, using either code-based logic or AI-powered evaluation.

Data Webhooks are designed for **custom integrations**, **event-driven workflows**, and **external signal ingestion**.

***

### 🛠️ What Is a Data Webhook?

A Data Webhook is an **HTTP endpoint** that:

* Accepts **incoming JSON data**
* Stores and forwards the data internally
* Triggers one or more **Reactions**
* Can be **shared** with other users

> Currently, Data Webhooks accept **JSON payloads** only.\
> Support for **plain text input** is coming soon.

***

### 🧠 How It Works

1. You create a **Data Webhook**
2. Sigrex generates a **unique webhook URL**
3. External systems send `POST` requests to this URL
4. Incoming data is:
   * Validated
   * Stored
   * Forwarded to all connected **Reactions**
5. Reactions process the data using **code or AI**

***

### ⚙️ Configuration Options

#### Name

Optional.\
Used for easier identification inside the platform.

***

#### Description

Optional.\
Explain the purpose of the webhook or the type of data it receives.

***

#### Webhook URL

Automatically generated by Sigrex.

Use this URL as the target endpoint for external `POST` requests.

***

#### Payload Format

* **Supported:** JSON (`application/json`)
* **Coming soon:** Plain text payloads

***

#### Key Protection

Enable this option to secure your webhook with a shared secret.

* When enabled:
  * You must define a **password**
  * Requests must include the header:

```
X-Key: <your-password>
```

* Requests without the correct key will be rejected

This helps prevent unauthorized or accidental data submission.

***

### 🔐 Security Notes

* Treat the webhook URL as **sensitive**
* Use **Key Protection** when sharing the webhook
* Rotate the key if it becomes exposed

***

### 🤝 Sharing Webhooks

Data Webhooks can be **shared with other users**.

When shared:

* Others can send data to the same webhook
* All incoming data is processed **exactly the same way**
* Connected Reactions will receive data regardless of sender

This makes Data Webhooks ideal for:

* Team-based workflows
* Community-driven data sources
* Multi-system integrations

***

### 🔁 Forwarding to Reactions

Every incoming payload is automatically forwarded to **all Reactions** attached to the webhook.

Reactions can:

* Parse and validate data
* Trigger logic written in code
* Call AI models for interpretation or classification
* Route data to other Sigrex components

> Data Webhooks themselves do **not** execute actions — Reactions define what happens next.

***

### 🧪 Example Request

```http
POST /data-webhook/<id> HTTP/1.1
Content-Type: application/json
X-Key: my-secret-key

{
  "event": "price_alert",
  "symbol": "BTCUSDT",
  "price": 67250,
  "source": "external-system"
}
```

***

### 🔗 Related Features

* [**Code**](/reaction/code-reaction.md) **or** [**LLM**](/reaction/llm-reaction.md) **Reactions** – Define how incoming data is processed
* [**Bot Webhooks**](/getting-started/webhook.md) – Trigger trading bots directly
* [**LLM Sessions**](/startegies/llm-session.md) – Scheduled AI analysis
* [**Chart Analysis**](/startegies/llm-session/chart-setup.md) **with** [**Signal Generation**](/startegies/llm-session/signal-generation.md) – AI-driven signals

***

### 🚫 Limitations

* JSON-only payloads (for now)
* No direct trading actions without Reactions
* No schema enforcement (data is passed as-is)


---

# 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.sigrex.io/reaction/data-webhook.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.