Comparing FMZ API Forwarding with Direct HTTP Signal Reception

Summary

The article compares two ways to deliver external trading signals to an FMZ strategy, using TradingView webhooks as the example. One route sends requests through the platform’s extended API, which forwards them to the strategy as interaction messages. The other runs an HTTP service alongside the strategy and receives requests directly. The article outlines the tradeoff: API forwarding adds a platform transfer step, while direct reception removes that step but requires more work to configure HTTPS securely.

A sample test sends concurrent requests through both routes, records arrivals, matches them against sent messages, and measures elapsed time. The reported observations show slightly lower average latency for direct HTTP and no lost messages through API forwarding during the test. The author cautions that the setup simulates requests locally rather than using real external traffic, and that network conditions could affect reliability. These results are a limited comparison, not a guarantee of speed or delivery under production conditions.

Key ideas

• The extended API forwards external requests to a strategy as interaction messages.
• A strategy can instead receive requests directly through a concurrent built-in HTTP service.
• The test compares message delivery by matching sent and received identifiers and measuring elapsed time.
• The observed test found slightly lower average latency for direct HTTP and no API message loss.
• The test used simulated requests, so its findings may not generalize to external network conditions.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.