FMZ Extended API Authentication, Permissions, and Robot Management
Summary
This FMZ reference explains how to create API keys with broad or method-specific permissions, interpret response codes, and read live-trading status values. It outlines two authentication approaches: signed token requests using a nonce and direct secret-key authentication. Examples show calling methods to list platform resources, inspect robots, send commands, and stop or restart live strategies. It also describes using direct requests to deliver webhook message bodies to a robot.
The document includes extensive Python and Go request examples and describes returned robot, log, profit, and chart data. Its practical value is platform administration and integration rather than a trading strategy or evidence about market returns. The examples expose credentials in request parameters and include a note about disabling certificate verification in one client example; implementations should handle secrets and transport security carefully. The reference is extensive, and the provided document excerpt is truncated, so it may not contain every interface detail or limitation.
Key ideas
- API keys can be restricted to selected extended API methods or granted broad permissions.
- Signed token requests use a nonce and signature, while direct authentication is described for supported calls.
- Response codes and robot status values help distinguish request failures from live-trading states.
- The API can support robot inspection, commands, and lifecycle actions such as stopping or restarting.
- Webhook requests can pass message content to a live robot through the command interface.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.