Why Binance API Order IDs May Not Work with FMZ GetOrder

Summary

The post describes a futures order placed through Binance’s API and a failed attempt to retrieve it with FMZ’s `exchange.GetOrder()` method. The exchange reports that the order does not exist, even though the author says it was placed successfully. By comparison, an order ID returned by FMZ’s own `exchange.Buy()` method can be retrieved with `GetOrder()`.

The example shows how the author submits a market order through FMZ’s API interface and passes the returned Binance order ID to the lookup method. It raises a practical question about whether IDs from direct API calls and IDs from FMZ’s built-in order methods are interchangeable. The post provides no answer or diagnosis, so it does not establish the cause or a fix. Traders using exchange wrappers can take from it the need to check how an adapter handles order identifiers and whether lookup methods support IDs from different order submission paths.

Key ideas

• The author reports that an order placed through Binance’s API cannot be retrieved using FMZ’s order lookup method.
• An order ID from FMZ’s built-in buy method can be retrieved in the same way.
• The post provides an example of direct API submission but does not identify the cause or solution.
• Users of exchange adapters should verify that order submission and lookup methods accept compatible identifiers.

Tags

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