For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

The Data Webhook URL is automatically generated by Sigrex.

The URL follows this format:

https://hook.sigrex.io/data/<webhook-hash>

For example:

https://hook.sigrex.io/data/71d3c761-5ee8-4ged-8400-7132ce6899d7

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:

  • 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



🚫 Limitations

  • JSON-only payloads (for now)

  • No direct trading actions without Reactions

  • No schema enforcement (data is passed as-is)

Last updated