Receiving TradingView Webhooks with an FMZ Strategy HTTP Service
Summary
The document describes routing TradingView strategy alerts into an FMZ strategy through its built-in HTTP service. It outlines an approach using an expected signal message format, IP allowlisting and password checks, then validating fields such as exchange selection, market, contract type, action, price, and amount before handling a trade. The workflow connects TradingView alert placeholders to the fields FMZ expects, so an alert can carry an order identifier, direction, and quantity to the receiving strategy.
The example’s operational walkthrough uses a TradingView alert and a perpetual market, with the alert body configured to match the strategy’s signal conventions. It explains that the receiving service processes the POST request and submits the corresponding exchange operation. This is integration guidance rather than evidence of a profitable strategy: the shown live test demonstrates signal delivery and synchronized trading in a simulation environment, not performance under live market conditions. The excerpt does not provide the full implementation, and the HTTP example relies on a shared password and IP filtering; the article notes HTTPS as an option for stronger transport security.
Key ideas
- A strategy’s built-in HTTP service can receive external trading alerts and pass their contents into order handling.
- Signal fields and TradingView alert placeholders must use matching action, market, contract, and quantity conventions.
- The example adds IP allowlisting and password verification before accepting requests.
- The described live test checks synchronized signal execution in a simulation environment, not profitability.
- Alert delivery and order execution depend on correctly validating and interpreting incoming message fields.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.