MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Automation

Webhook & External Signal Management

Receive trading signals from external systems (TradingView, custom apps) at a secret endpoint and route eligible ones safely to market — the third entry point into the controlled path, alongside manual and strategy trading.

Where you will find this

Webhooks, Execution Log.

Functional Scope

Each webhook exposes a unique, secret endpoint. An external system posts a signal to it; the platform records the signal, validates it, and — only for a deployed, enabled webhook — turns it into orders on the broker accounts you have mapped. Every incoming signal is logged before any validation, so nothing is ever silently dropped.

Safe by construction

Webhook orders go through Risk and Order Management like every other order — never straight to the broker. Trading quantity always comes from your mapping configuration, never from the incoming signal, and each broker execution is isolated so one failure can’t affect the others.

The module includes:

Webhook Management Webhook Endpoint Management Webhook Configuration Deployment Management Operational Status Management Broker Account Mapping Signal Processing Order Generation Signal Log Management Execution Log Management Webhook Testing Signal Replay Traceability Search Audit Webhook Management

You can:

Create Webhook Modify Webhook Delete Webhook View Webhook Deploy Webhook Enable Webhook Disable Webhook

Each webhook will operate independently.

Webhook Endpoint Management

Each webhook will expose a unique endpoint.

The endpoint may receive trading signals from external systems including:

TradingView MyAlgo Third-party Trading Platforms Custom Applications

The platform remains provider independent.

Webhook Configuration

Each webhook will maintain:

Name Description Endpoint Trading Product Deployment Status Operational Status Business Owner

Configuration remains independently manageable.

Deployment Management

Every webhook will support lifecycle management.

Typical lifecycle states include:

Draft Configured Deployed Suspended Retired

Only deployed webhooks may process trading signals.

Operational Status Management

Operational status includes:

Enabled Disabled

Disabled webhooks will continue to record incoming signals but does not generate trading orders.

Broker Account Mapping

Each webhook may be mapped to one or more broker accounts.

Each broker mapping may define:

Broker Account Trading Product Fixed Quantity

or

Quantity Multiplier

Each broker account will execute independently.

Different broker accounts may use different quantities.

Signal Processing

For every incoming signal the platform will:

Receive Signal Record Signal Validate Signal Validate Deployment Status Validate Operational Status Resolve Broker Mapping Determine Quantity Generate Orders Record Execution Results

Processing remains fully traceable.

Order Generation

Webhook signals will generate trading orders.

Generated orders will follow the business rules defined within Order Management.

Where supported, Market Orders is generated.

Where Market Orders are unavailable, the platform will generate the nearest equivalent executable order while preserving the intended business outcome.

Broker Session Validation

Prior to order generation the platform will verify broker connectivity.

Where broker authentication is unavailable:

Order generation for that broker will fail. The failure is recorded.

Failure of one broker account does not prevent execution for other mapped broker accounts.

Multi-Account Execution

A single incoming signal may generate multiple trading executions.

Each execution remains independent.

Each execution will maintain its own execution status.

Signal Log Management

Every incoming webhook request will generate one Signal Log record.

Signal logging will occur before business validation.

Each Signal Log will maintain:

Timestamp Webhook Source Application Instrument Trading Side Raw Payload Validation Status Processing Status Signal Type

Signal Types may include:

Production Test Replay

Processing Status may include:

Accepted Ignored Invalid Payload Unknown Webhook Disabled Not Deployed Failed

You can search Signal Logs using:

Webhook Instrument Source Application Signal Type Processing Status Date Range Execution Log Management

Execution Log remains separate from Signal Log.

One Signal Log may generate one or more Execution Logs.

Each Execution Log includes:

Timestamp Related Signal Broker Account Instrument Trading Side Quantity Trading Product Order Status Execution Status Broker Response Signal Type

You can search Execution Logs using:

Broker Instrument Trading Side Execution Status Signal Type Date Range Webhook Testing

Every webhook will support testing.

Testing modes includes:

Validation Only

The complete business processing pipeline will execute without broker order submission.

End-to-End Test

The complete business processing pipeline will execute including broker order generation.

Signal Replay

Previously received signals is replayable.

Replay will create a new processing request using the original signal.

Replay will execute using:

Current Webhook Configuration Current Broker Mapping Current Quantity Configuration

Replay modes includes:

Validation Replay End-to-End Replay

Replay will never modify historical records.

Each replay will generate:

New Signal Log New Execution Logs Traceability

The platform will maintain complete end-to-end traceability.

Every signal remains traceable from:

Incoming Signal

↓

Signal Log

↓

Business Validation

↓

Broker Mapping

↓

Order Generation

↓

Broker Execution

↓

Authorised users is able to search webhook information using:

Webhook Endpoint Deployment Status Operational Status Broker Account Instrument Signal Type Processing Status Execution Status Date Range Business Rules Every webhook will have a unique identifier. Every webhook will expose a unique endpoint. Every incoming signal will always be recorded. Signal logging will occur before business validation. Signal logging will occur even when a webhook is disabled. Disabled webhooks will never generate trading orders. Undeployed webhooks will never generate trading orders. Invalid signals will still be recorded. Trading quantity will always originate from webhook configuration. Incoming signals will never determine trading quantity. Broker authentication is validated before execution. One incoming signal may generate multiple broker executions. Failure of one broker execution does not affect other broker executions. Signal Log and Execution Log remains permanently linked. Production, Test and Replay signals remains distinguishable. Replay will never modify historical records. Replay will always generate new Signal Log and Execution Log records. Audit Requirements

The platform will maintain an immutable audit trail including:

Webhook Creation Configuration Changes Deployment Enable / Disable Broker Mapping Changes Signal Receipt Signal Validation Order Generation Execution Results Test Execution Replay Execution Lifecycle Changes Dependencies

This module depends upon:

BRS-002 Broker Connectivity & Account Management BRS-004 Order Management BRS-021 Event Management BRS-025 Notification Management BRS-029 Audit & Activity Logging BRS-035 Platform Operations Management

This module may be utilised by:

Strategy Management Strategy Deployment & Execution Engine Manual Trading Terminal Risk Management Portfolio Management Integration Management Out of Scope

The following are outside the scope of this module:

Broker-specific API implementation Network communication protocols Authentication mechanisms Message queue infrastructure API gateway implementation Transport security implementation

These responsibilities belong to specialised infrastructure or integration components.

My Strategies — trading a TradingView signal

My Strategies is where an external signal becomes a trade. A strategy is built, given the accounts and arms it should act on, deployed and then armed. It shares the one execution engine with the webhook path — there is no second engine behind this tab.

  • The execution window, the trading days and the square-off time are set at group level, so every arm of a group shares them.
  • A signal arriving outside the window is dropped, and the drop is recorded with its reason rather than discarded silently. That record is the first place to look when a signal did not trade.
  • Deployed strategies appear as cards beside the builder rather than a panel below it.

Signal Rules — sequencing what a signal does

Signal Rules is the sequencing layer: it decides what has to happen, and in what order, once a signal arrives. There is one sequencing engine, implemented on both the browser and the server side, so a rule behaves the same whether it is being previewed or run live.

  • The live path asks about fills rather than assuming a leg was established, so a sequence does not advance on an order that has not actually filled.
  • A rule controls ordering and conditions. It does not forecast the signal it is acting on.

Webhook endpoints

  • A webhook URL is identified by its hash alone, and there is exactly one per algo.
  • The URL is the credential — anyone holding it can post a signal to it, so it should be treated like one.
  • A webhook delivering a signal is not the same as the signal trading. Whether it trades depends on the algo’s window, days and conditions.

Set up a webhook

  1. Create a webhook — you receive its secret endpoint token once. Keep it safe.
  2. Map one or more broker accounts, each with its own fixed quantity (or multiplier).
  3. Deploy the webhook and enable it. A disabled or undeployed webhook still logs signals but generates no orders.
  4. Point your external system at /webhooks/ingest/<token>.
  5. Use Test (validation-only) to dry-run the pipeline, and Signal Replay to re-run a past signal against the current configuration.