Fetch the order book, keeping the rows that could not be read.
getOrders returns the first half of this. A host that renders the book
needs the second half too: "2 rows from the broker could not be read" is a
thing the trader must see, and a quietly shorter list is not.
Fetch the order book for reconciliation (maps to broker-agnostic orders).
Read the analyzer mode the SERVER is in.
Analyzer mode is a server-side global in OpenAlgo: get_analyze_mode()
decides where every order goes, and it is flipped at
POST /api/v1/analyzer/toggle. It is not a per-order flag, there is no
mode field on the placeorder payload, and one added there would be read by
nothing. So this client never asserts a mode. It asks for the server's,
and place refuses when the answer disagrees with the caller's belief.
Answers younger than maxAgeMs are reused, so a host that polls the books
(whose sandbox responses carry the mode already) never pays for this call.
Release a claim after the host has established what really happened, for instance by finding no such order in a freshly fetched book.
Deliberately manual. Nothing in this library can safely decide on its own that an ambiguous order did not reach the exchange.
Whether a client order id is known to have reached the broker.
'ambiguous' is the one worth handling: the request left and the outcome is
unknown, so the order may be live. A host should say so and offer the order
book, not a retry button.
The minimal broker write interface the
OrderEnginedrives: place / modify / cancel.OpenAlgoTradeFeedimplements this. Distinct from the base-tierTradeFeed(a higher-level place + subscribe shape inopenalgo-charts): implementOrderFeedfor the engine's write path.