Signal Delivery

After subscribing to a signal feed, you need to configure how signals are delivered to your trading infrastructure. Nexgent Signals supports two delivery methods: the Nexgent Trading Engine (recommended) and Webhooks.

Delivery Methods Comparison

1. Nexgent Trading Engine (Recommended)

The recommended way to receive signals is by connecting to your self-hosted Nexgent Trading Engine. This enables automated trade execution based on the signals you receive.

Overview

When connected, signals flow directly from Nexgent Signals to your trading engine:

Nexgent Signals → Your Trading Engine → Agent Evaluation → Trade Execution

Setup Guide

Create API Key in Trading Engine

First, create an API key in your trading engine that has permission to receive signals:

1. Open your trading engine dashboard
2. Navigate to the Integrations page in the sidebar
3. In the API Keys section, click Create Key
4. Enter a name (e.g., "Nexgent Signals")
5. Select the Restricted tab
6. Enable the Signals scope (read & write trading signals)
7. Click Create API Key
8. Copy the API key — it's only shown once

Navigate to Integrations in your Trading Engine to create a new API key

⚠️

Store your API key securely. If you lose it, you'll need to create a new one.

Configure Delivery in Nexgent Signals

1. Go to the Signals Config (opens in a new tab) page
2. Select Nexgent open-source trading engine as the delivery method
3. Enter your engine's base URL:

   https://your-engine.example.com
4. Enter the API key you created in Step 1
5. Click Save endpoint

Enter your Trading Engine URL and API key in the configuration tab

Test the Connection

1. Click the Send test button
2. Verify the status shows "Connected"
3. Check your trading engine's signal log to confirm receipt

Verify the connection is successful with a test signal

Troubleshooting Connection

2. Webhook Delivery

Webhook delivery sends signals to any HTTP endpoint you specify. This enables custom integrations with your own trading systems, notification services, or third-party platforms.

Use Cases

• Custom Trading Bot: Receive signals and execute trades with your own logic.
• Notifications: Send alerts to Telegram, Discord, Slack, etc.
• Logging & Analytics: Store signals in a database for backtesting or analysis.

Setup Guide

const express = require('express');
const app = express();
app.use(express.json());
 
app.post('/nexgent/signals', (req, res) => {
  const signal = req.body;
  console.log('Received signal:', signal);
  // Your logic here
  res.status(200).json({ received: true });
});
 
app.listen(3000);

Signal Payload Structure

Both delivery methods receive the same JSON payload:

{
  "signalId": "sig_abc123",
  "signalType": "Velocity",
  "tokenAddress": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263",
  "symbol": "BONK",
  "signalStrength": 4,
  "activationReason": "Sustained momentum with increasing volume",
  "source": "nexgent-signals",
  "timestamp": "2025-01-24T10:30:00Z"
}

Security Best Practices

• Use HTTPS: Always use encrypted connections in production.
• Validate Requests: Check the Authorization header if you configured an API key.
• IP Allowlisting: If possible, restrict incoming traffic to Nexgent's known IPs.
• Rate Limiting: Protect your endpoint from abuse.