Using FMZ Extension APIs to Manage Trading Robots and Receive Alerts

Summary

This guide explains how programs can call FMZ’s extension API to retrieve account and robot information, issue commands, and manage robot states. It covers API key creation and per-method permissions, response and status codes, request parameters, and an MD5-based signature that combines the API version, method, arguments, nonce, and secret key. Python and Go examples illustrate authenticated calls, including robot listing, detail retrieval, restart, stop, and command operations.

The guide also describes direct secret-key authentication for command delivery, including receiving webhook bodies from TradingView, and documents log, profit, and chart data fields. It is operational documentation rather than a trading strategy: it contains no market analysis or performance evidence. Authentication mode, endpoint permissions, nonce handling, and request formatting affect whether calls succeed. Direct command URLs can trigger live robot actions, so the API key’s permissions and handling are central to safe integration.

Key ideas

• Extension API keys can be scoped to selected methods or granted broader access.
• Token authentication signs request fields with an MD5 hash and requires a changing nonce.
• The API supports robot queries and control operations, with documented response and robot status codes.
• Direct authentication can route webhook messages to a robot command interface.
• The guide documents integration mechanics but gives no evidence about trading performance.

Tags

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