Webhooks
Vantixs webhooks let you receive external trading signals and route them into your strategy pipeline. The primary integration is with TradingView, but any system capable of sending HTTP POST requests can trigger signals.
During the BETA period, webhook signals trigger paper trading actions only. Live trading with real capital is planned for a future release.
How Webhooks Work
When an external system (e.g., a TradingView alert) sends a POST request to your Vantixs webhook URL, the signal enters the WebhookSignalProcessor queue for asynchronous processing. Depending on your webhook mode, the signal either executes directly against risk checks or routes through a saved strategy pipeline for indicator validation first.
Signal Flow
External alert fires
TradingView (or another source) sends an HTTP POST to your unique webhook URL.
Token verification
Vantixs validates the HMAC token included in the request. Invalid tokens are rejected immediately.
Signal queued
The signal is added to the WebhookSignalProcessor Bull queue for reliable, async processing.
Mode routing
In **Direct** mode the signal proceeds straight to risk checks and order placement. In **Pipeline** mode it routes through your saved strategy for indicator validation first.
Execution
After passing all checks, the signal triggers a paper trading action on your connected exchange.
Logging
Every signal is logged with its status (received, executed, rejected, or failed) for audit and replay.
TradingView Integration
TradingView is the most common webhook source. You can connect any Pine Script alert to Vantixs in a few steps.
Setting Up a TradingView Alert
Create a webhook in Vantixs
Go to **Settings > Webhooks** and click **Add Webhook**. Fill in the name, mode, exchange API key, and sizing configuration.
Copy the webhook URL
After creation, Vantixs provides a unique URL in the format: ``` https://api.vantixs.com/webhooks/tradingview/:userId/:token ``` Copy this URL immediately --- the secret token is shown only once.
Open TradingView
Navigate to the chart where your Pine Script indicator or strategy runs.
Create an alert
Click the alert button, configure your condition, then scroll down to the **Webhook URL** field and paste your Vantixs URL.
Set the alert message
Use the JSON payload format below in the **Message** field of the TradingView alert.
Save the alert
TradingView will now POST to Vantixs every time the alert fires.
Payload Format
TradingView alerts should send a JSON body. The minimal required fields are:
{
"action": "buy",
"symbol": "{{ticker}}"
}
| Field | Type | Description |
|---|---|---|
code | string | Trade action: code code code |
code | string | Trading pair symbol (use TradingView code |
The
{{ticker}}BTCUSDTWebhook Management
Manage all your webhooks from Settings > Webhooks in the Vantixs web app.
Creating a Webhook
Click Add Webhook to open the creation dialog. Configure the following:
| Field | Description |
|---|---|
| Name | A descriptive label, e.g., "BTC RSI Strategy" |
| Mode | Direct (signal goes straight to risk checks) or Pipeline (signal routes through a saved strategy first) |
| Exchange API Key | Which exchange account receives the orders |
| Strategy | (Pipeline mode only) The saved strategy used for indicator validation |
| Sizing Type | Fixed Quantity or % of Balance |
| Sizing Value | The numeric amount for position sizing |
The secret token is displayed only once after creation. Copy it immediately. If you lose the token, you can regenerate it, but any existing TradingView alerts using the old token will stop working.
Token Security
Each webhook is secured with an HMAC token:
- Tokens are generated server-side and shown once at creation time
- Only a masked preview is visible after the initial display
- You can regenerate a token at any time --- this immediately invalidates the previous one
- Maximum of 5 webhooks per account
Editing and Deleting
Each webhook card displays its URL, token preview, mode, and sizing configuration. From the card you can:
- Copy the webhook URL to your clipboard
- Regenerate the token (invalidates the old one)
- Delete the webhook and all its signal history
Signal History and Replay
Every signal received by a webhook is logged and available in the Signal History section below the webhook list.
Signal Statuses
| Status | Meaning |
|---|---|
| Received | Signal accepted and queued for processing |
| Executed | Signal successfully processed and order placed |
| Rejected | Signal failed validation (e.g., invalid payload, risk check failure) |
| Failed | Processing error occurred |
| Replayed | A previously failed/rejected signal was re-sent |
Replaying Signals
Failed or rejected signals can be replayed with a single click. This re-sends the original payload through the webhook processing flow and creates a new log entry with the
replayed- Retrying after a temporary exchange connectivity issue
- Re-processing after fixing a configuration problem
- Testing signal handling without waiting for a new TradingView alert
Use Cases
Common Webhook Use Cases
TradingView Alerts
Connect Pine Script alerts to trigger paper trades automatically based on your custom indicators
Custom Scripts
Send signals from Python, Node.js, or any language that can make HTTP POST requests
Third-Party Signals
Route signals from other platforms or signal providers through your Vantixs risk management
Multi-Strategy Routing
Use Pipeline mode to validate external signals against your visual strategy before execution
Signal Auditing
Log and review all incoming signals with full payload visibility and replay capability
Automated Testing
Replay failed signals to verify fixes without waiting for live market conditions