Release Notes¶

This public changelog keeps only user-facing upgrade, API, and behavior changes.

v1.4.110 · 2026-05-26 — 🔴 Architecture convergence and trade / quote reliability¶

All v1.4.109 users are encouraged to upgrade, especially if you use live trade writes, quote subscriptions / order books / market state, multiple public surfaces, long-running daemons, or automation scripts.

Trade write and read paths now validate backend responses more strictly. Place, modify, cancel, reconfirm, order / fill refresh, and history order / fill queries return clear errors when the backend response is missing required fields, has a mismatched status, or no longer matches the request.
Order ID, order IDEx, modify / cancel fields, simulated and crypto account response headers, max-trade-quantity, order fee, and margin-ratio paths were further aligned to reduce cases where an order placed successfully cannot be queried, modified, or cancelled consistently.
Quote subscriptions, quote, snapshot, order book, K-line, market state, and crypto LV2 paths now separate cache and push routing by broker / session / security key more consistently, improving mixed subscriptions, multi-broker routing, stale-cache behavior, and order-book depth handling.
quote-rights / user-info output is closer to the official OpenD GUI: user info, quota, and quote rights are shown as separate sections, with more complete Hong Kong, US, A-share, Singapore, Japan, crypto, futures, and options rights.
futucli quote-rights and futucli user-info now fail fast with structured errors when the gateway is not running, the port is wrong, or the gateway is unreachable. json / jsonl output is usable by agents, CI, and quantitative scripts without an external timeout wrapper.
Several REST / MCP / CLI / Gateway / gRPC endpoints now share a surface-spec contract for parameters, scopes, defaults, and exposure state, making unknown fields, invalid input, and unavailable endpoints fail more consistently.
used-quota, reconfirm-order, option-chain Greek filters, and several account / quote helpers are more consistent across public surfaces.
Gateway internals were split into clearer core / qot / trd boundaries. Cache, push, broker runtime, reconnect, and startup state are more centralized, and release / pre-push guardrails now include line-count, PII, Cargo.lock drift, and releasegate checks.
Futu API v10.6.6608 endpoints are not included in this release; they will be delivered separately in a later version.

v1.4.109 · 2026-05-16 — 🔴 Broker auth and live trade-write fixes¶

All v1.4.108 users are encouraged to upgrade, especially if you use live trade writes, FTAPI binary clients, multi-broker account login, or broker auth from networks where direct domain access is unreliable.

Fixed a live place-order issue where a new order could receive the result of an earlier order. Backend trade request IDs are now regenerated for each request instead of reusing a packet-derived string.
Native-protocol trade writes such as place, modify, and cancel no longer fail locally before reaching the backend because of an overly strict connection-ID replay check.
Broker auth now prefers the WebTCP short-connection path, server-provided address pools, and the fallback chain instead of approximating the flow with ordinary system DNS / HTTPS.
Fixed the rustls provider panic that could stop broker auth during startup.
Order IDs are handled more consistently across trade writes, order queries, fill queries, and push delivery, reducing cases where modify, cancel, or query cannot find the order returned by place-order.
Ended-order cancel attempts, stale backend order echoes, and successful responses missing required order identifiers now fail more clearly instead of looking like empty success.
Real-environment verification covered place, modify, cancel, and the matching trade pushes.

v1.4.108 · 2026-05-06 — 🔴 Quote subscription and account discovery fixes¶

All v1.4.107 users are encouraged to upgrade, especially if you use real-time quote subscriptions, Hong Kong futures main-link symbols, account listing, App-visible card numbers, or max-trade-quantity queries.

Fixed quote push decoding for newer server frames. Hong Kong futures main-link symbols and some real-time quote subscriptions no longer subscribe successfully but receive no data.
Main-link, current-month, and next-month futures aliases now route incoming quote pushes back to the symbol requested by the client, improving order book, quote, and ticker delivery.
Account discovery now defaults to an App-visible account view. It keeps enabled crypto and equity-incentive business accounts, while hiding internal futures-only simulated rows that the App does not show as standalone accounts.
CLI / MCP / REST expose a single user-facing card_num, and JSON acc_id values are serialized as strings to avoid precision loss in JSON and table tooling.
futucli account groups rows by broker and by real / simulated / disabled status. Market columns now show names instead of raw numeric market IDs.
GetMaxTrdQtys response projection was further aligned, including Option IM side requests and several market-specific response fields.
Malformed trade, quote, and system request bodies now return clear errors instead of empty success or no-response behavior.

v1.4.107 · 2026-05-04 — 🔴 Asset reads and trade calculation fixes¶

All v1.4.106 users are encouraged to upgrade, especially if you use funds, positions, cash logs, simulated accounts, universal accounts, or trade calculation endpoints.

Simulated-account funds, positions, orders, and fills now use simulated account paths instead of real-account query paths.
Funds and position refreshes are separated by account, currency, and asset category. Backend refresh failures and cold-cache in-flight requests now return clear errors instead of empty success.
Cash log, cash detail, business group, margin info, account flag, and bond endpoints derive backend account and market data from authenticated account state. Requests fail clearly when that state cannot be derived.
History orders, history fills, order refresh, fill refresh, order fee, margin ratio, and max-trade-quantity endpoints now validate market, security, and backend-route requirements more strictly.
MCP / CLI cash-log, cash-detail, account-flag, and bond output includes more user-visible backend fields, reducing differences between surfaces.

Migration note for callers upgrading from versions before v1.4.99: Universal and futures accounts must now pass currency explicitly when calling /api/funds (integer: 1=HKD / 2=USD / 3=CNH / 4=JPY / 5=SGD / 6=AUD / 7=CAD / 8=MYR); omitting it returns a MissingCurrency error. This behavior shipped in v1.4.106; the older (≤ v1.4.99) "returns a value but with a misaligned currency tag" pattern was a now-fixed bug. Pass the currency integer to migrate. See REST API doc.
Unlock-trade cooldown now counts only trade-password errors. gRPC trade requests can carry idempotency-key metadata.

v1.4.106 · 2026-05-02 — 🔴 Funds queries and account isolation fixes¶

All v1.4.105 users are encouraged to upgrade, especially if you use funds queries, simulated accounts, universal accounts, futures accounts, or restricted API keys.

Fixed /api/funds currency validation: single-market and simulated accounts return their native currency, while universal and futures accounts still validate the requested currency strictly.
Funds snapshots are cached by account, asset category, and currency, so different query shapes no longer overwrite one another.
REST / MCP / CLI / SDK now describe cash consistently as summary cash in the response currency, not a sum across currency rows.
Trade-write endpoints no longer reveal whether another account exists through card_num suffix resolution when account whitelists are enabled.
futucli funds --market is now optional; if the requested and returned currencies differ, the CLI prints a stderr warning.

v1.4.105 · 2026-04-30 — 🔴 Order reliability, funds currency, and push filtering¶

All v1.4.104 users are encouraged to upgrade.

Place-order now waits for trading confirmation before exposing the order, with short-window duplicate-submit protection.
/api/funds returns a structured InvalidCurrency error when the requested currency is not supported by the account.
Multi-market universal account detection is more robust when cached account metadata drifts.
/api/static-info rejects explicit empty lists instead of triggering broad server queries.
REST WebSocket, native TCP, gRPC, and MCP trade pushes now use the same account and market whitelist filtering.
Client-visible unlock-trade, gRPC permission, and funds-currency errors are redacted.

v1.4.104 · 2026-04-29 — 🔴 Unified auth entry points and security fixes¶

All v1.4.103 users should upgrade.

When API keys are configured, unauthenticated native TCP listening is closed by default unless explicitly enabled for legacy clients.
Fixed allowed_card_nums being treated as unrestricted before expansion.
Trade-unlock cooldown now applies across all broker routes.
Login failures show clearer error codes and hints without exposing credential contents.
REST subscribe requests must explicitly say subscribe or unsubscribe; invalid tickers no longer succeed silently.
Funds currency warnings and common errors are more consistent across REST, CLI, and MCP.

v1.4.103 · 2026-04-29 — 🔴 Duplicate submit, account isolation, and universal-account currency¶

Live-trading, restricted-key, and universal-account users should upgrade.

Fixed a duplicate-submit risk where a retry could be triggered by an intermediate order status.
Restricted API keys enforce account isolation consistently across REST, gRPC, MCP, and native protocol entry points.
Universal-account funds queries support explicit --currency, keeping values and currency labels aligned.
card_num can be used directly in key configuration for account scoping.
MCP HTTP mode resolves caller identity from the per-request Bearer token instead of falling back to the startup key.

Recommended for multi-user machines, long-running daemons, and automation.

Fixed last_close_price scaling.
/api/subscribe now rejects invalid or empty symbols instead of returning empty success.
Long-running daemons reuse fresh SMS credentials instead of sending another SMS that invalidates the code the user just entered.
Credential and device files are tightened to 0600 on Unix.
Missing trd_env, malformed config sections, and invalid key files now fail clearly.
/api/unsub-acc-push now actually unsubscribes.

v1.4.101 · 2026-04-28 — 🟢 Option-chain and date-boundary fixes¶

Mostly relevant to option-chain, expiration-date, and market-timezone users. Users already on v1.4.100 can upgrade as needed.

Option expiration queries support safe default date windows.
Date boundaries are interpreted in the relevant market timezone.
Option entitlement, missing expiration-date data, and unknown enums are handled more strictly.

v1.4.100 · 2026-04-28 — 🟡 Option-chain and option quote fixes¶

Recommended for option-chain, option snapshot, or option subscription users.

Fixed option-chain defaults, date de-duplication, owner-market detection, and Greek filtering.
Option snapshots include more volatility, Greek, and expiration fields.
Option subscription fallback, contract static info, and CLI JSON output are more consistent.
Several quote endpoints now reject invalid input explicitly.

v1.4.99 · 2026-04-27 — 🟢 Input validation and output-format fixes¶

Ticker statistic, interest-rate, and spread-table endpoints handle error responses and unknown fields more strictly.
CLI JSONL output is more stable for machine readers.
Low user impact; mainly improves error visibility.

v1.4.98 · 2026-04-27 — 🟡 New query endpoints and feedback fixes¶

Recommended if you need richer quote or account fields.

Added or completed token-state, spread-table, risk-free-rate, and related quote fields.
Fixed option-chain routing, default date range, CLI JSON output, and MCP state fields.
REST quote paths use stricter validation to avoid silently ignored parameters.

v1.4.97 · 2026-04-27 — 🟡 Account detection and long-run observability¶

Crypto-account funds, positions, fills, orders, and cash-log queries no longer return silent empty results.
/api/accounts includes a label that helps distinguish standard cash and crypto accounts.
Long-running daemon reconnect, cooldown, and health signals are clearer.
Users only doing standard stock or option queries can upgrade as needed.

v1.4.96 · 2026-04-26 — 🔴 Option-chain, order, and quote hotfixes¶

Users of options, order queries, or K-line endpoints should upgrade.

Option-chain default queries no longer return empty data when a safe date range can be inferred.
Order, modify-order, cancel-order, and order-query behavior is more reliable in multi-account scenarios.
Market-state, K-line date, and futures-related error hints were fixed.
CLI kline --count now defaults the end time to now.

v1.4.95 · 2026-04-26 — 🟡 Account, margin, and bond queries¶

Recommended if you need advanced account or bond data.

Added margin info, account flags, bond total asset, single-bond asset, bond positions, questionnaire state, and bond trade reminder queries.
REST, MCP, CLI, and gRPC use consistent naming and errors for the new queries.
Unsupported server-side capability returns a clear error instead of silent fallback.

Long-running login keepalive, signature refresh, and credential persistence are more robust.
Cash-log, position cost, option Greeks, and quote-entitlement fields are more complete.
New proactive refresh behavior is opt-in by environment variable.

v1.4.93 · 2026-04-26 — 🔴 Trading, quote, and long-run stability fixes¶

Recommended for all users on v1.4.90-v1.4.92.

Fixed order visibility, history-order overwrite, market state, and K-line subscription issues.
Long-running broker authorization can refresh automatically, reducing manual restarts.
History-fill and empty-data error messages are more accurate.
Added multi-version regression checks to reduce future drift.

v1.4.92 · 2026-04-25 — 🟡 Auto-reconnect and regression checks¶

The daemon can trigger an in-process reconnect when quote login state is lost.
Multi-version behavior checks help catch compatibility drift between shipped versions.
Older documentation index noise was reduced.

v1.4.91 · 2026-04-25 — 🟡 Reconnect wiring and error-message polish¶

Quote reconnect triggering was completed for long-running daemons.
Market-state, history-K-line, and trade-query errors are clearer.
Maintenance release; API shape is largely unchanged.

v1.4.90 · 2026-04-25 — 🔴 v1.4.86-v1.4.89 regression hotfix¶

Recommended for users on v1.4.86-v1.4.89.

Fixed regressions in order cache, K-line subscription, quote market detection, and trade queries.
Account-level error cooldown prevents one failing account from spamming logs.
REST and native-protocol paths are more consistent for history K-line and quote market selection.

v1.4.89 · 2026-04-25 — 🟢 Market detection and test coverage¶

Market routing now prefers server-provided account cache metadata over code prefix guesses.
Added broader endpoint tests and benchmarks to reduce quote/trade routing drift.
Low user-visible impact; users on v1.4.88 can upgrade as needed.

v1.4.88 · 2026-04-25 — 🟢 Code-quality maintenance¶

Added API comments, clearer errors, and more tests.
/api/history-kline accepts a single symbol shorthand.
No major user-visible behavior change.

v1.4.87 · 2026-04-25 — 🟢 Audit logs and timezone flag¶

Audit log file permissions are tightened by default.
CLI adds --tz for viewing timestamps in a chosen timezone.
Logging to temporary directories prints a warning.

v1.4.86 · 2026-04-24 — 🟡 REST legacy write endpoints locked down¶

Users of REST trade-write endpoints without API keys should review this change.

Without a keys file, REST place-order, modify-order, cancel-order, unlock, and other write endpoints now reject by default.
Read-only quote and account queries are unaffected.
Errors now point users toward key configuration before enabling write access.

v1.4.85 · 2026-04-24 — 🟢 Public API docs completed¶

REST, gRPC, and MCP reference docs were completed with consistent examples.
Download, quick-start, and guide pages were updated.
Documentation-only release; users on v1.4.84 can skip it.

v1.4.84 · 2026-04-24 — 🔴 Security fixes and compatibility migrations¶

All v1.4.83 users are encouraged to upgrade.

REST write endpoints reject by default when no API key is configured.
MCP parameter aliases and response shapes are more compatible.
Quotas, error enums, and metrics are more complete.
Migration guidance helps users move from older key configurations.

v1.4.83 · 2026-04-24 — 🟡 Query fixes and push self-healing¶

Positions, funds, and K-line endpoints are more stable on boundary inputs.
Missing trade-push data triggers cache refresh instead of silent stale state.
CLI and MCP parameter aliases are more consistent.

REST subscribe requests now fail clearly on missing fields and invalid input.
Order cache entries are not overwritten by later empty responses.
Several history-query endpoints no longer return silent success on bad parameters.

Users who need SMS verification on first login or reauthorization should upgrade.

Login state after SMS verification is persisted correctly.
Restarting no longer repeatedly triggers SMS because authorization state was not saved.
Credential save/load paths handle empty initial state more reliably.

v1.4.80 · 2026-04-24 — 🔄 Structure maintenance¶

Push parsing, handler dependency injection, and protocol translators continued to be modularized.
No user-visible API change; users on v1.4.79 can skip it.

v1.4.79 · 2026-04-24 — 🔄 Architecture maintenance¶

Trade and quote handlers were further split to reduce future change risk.
Persistence schema migrations are clearer.
No user-visible API change.

v1.4.78 · 2026-04-24 — 🔄 Parser and large-file cleanup¶

Push parser coverage for malformed input improved.
Large files were further split.
User-visible behavior is largely unchanged.

v1.4.77 · 2026-04-23 — 🔄 Dependency injection and pre-push checks¶

Trade handlers were slimmed down and more logic moved into dedicated modules.
Local checks are stricter before release.
No user-visible API change.

v1.4.76 · 2026-04-23 — 🟢 SMS timing hints and cash-log audit¶

SMS-verification hints are clearer.
Account cash-log errors are more accurate in boundary cases.
Maintenance release; general users can upgrade as needed.

Improved authorization-state persistence after first login.
Missing or damaged credentials return clearer hints.
Recommended for users still seeing repeated SMS verification loops.

v1.4.74 · 2026-04-23 — 🟡 Account and history-query fixes¶

Crypto-account, history-order, history-fill, and K-line date errors are more accurate.
REST flat-body and SDK-style field compatibility improved.
Recommended for v1.4.73 users affected by these areas.

v1.4.73 · 2026-04-23 — 🔴 Trading and credential fixes¶

All v1.4.72 users are encouraged to upgrade.

Fixed multiple issues in trade unlock, conditional orders, modify-order, history queries, and credential persistence.
History orders and fills are more stable with pagination and filters.
Market-state and futures-related queries are more accurate.

v1.4.72 · 2026-04-23 — 🔴 History-query and REST compatibility fixes¶

History K-line, history-order, and history-fill queries accept more SDK-style inputs.
Date and timezone handling follows the target market.
REST errors are more specific and avoid suggesting fields that do not apply.

v1.4.71 · 2026-04-23 — 🔴 HK futures state, order status, and TLS fixes¶

HK futures market state and order-status mapping were fixed.
History-order and history-fill date conversion follows market timezone.
HTTPS client configuration was tightened for production use.

v1.4.70 · 2026-04-23 — 🔴 Credential regression and history-fill status¶

Fixed credential save/load regression.
History-fill status fields are more accurate.
Recommended for users on v1.4.68 or v1.4.69.

v1.4.69 · 2026-04-23 — 🔄 Code refactor¶

Structure changes with little user-visible behavior impact.
Users on v1.4.68 can skip it.

v1.4.68 · 2026-04-23 — 🔴 Funds currency and multi-market timezone fixes¶

Single-market account funds return the account native currency instead of mislabeling the requested currency.
US, JP, AU, and CA history-query timezones were fixed.
Futures and options market detection is more accurate.

v1.4.67 · 2026-04-23 — 🔴 History queries and market detection¶

History orders, history fills, and K-line queries are more reliable for multi-market accounts.
Futures market and trade-market inference is more accurate.
Affected users should upgrade.

v1.4.66 · 2026-04-23 — 🔴 History-order filtering¶

/api/history-orders and /api/history-order-fills market filters were fixed.
Resolves missing history data for some accounts.

v1.4.65 · 2026-04-23 — 🔄 Test infrastructure maintenance¶

Gateway integration-test infrastructure was improved.
No user-visible behavior change; users on v1.4.64 can skip it.

v1.4.64 · 2026-04-22 — 🔴 2FA account query fixes¶

Funds, positions, and cash-log queries for 2FA accounts use the correct account route.
Related endpoints no longer return empty data or route errors due to incomplete routing.

v1.4.63 · 2026-04-22 — 🔄 Maintenance refactor¶

Handler modularization and dependency cleanup continued.
No user-visible API change.

v1.4.62 · 2026-04-22 — 🔄 Quote-handler split¶

Quote handlers began moving into smaller modules.
No user-visible API change.

v1.4.61 · 2026-04-22 — 🔄 Trade-handler split¶

Trade handlers continued to be modularized.
No user-visible API change.

v1.4.60 · 2026-04-22 — 🔄 Handler modularization begins¶

Large handler files began to be split.
No user-visible API change.

v1.4.59 · 2026-04-22 — 🔄 Market-routing precision¶

Market routing now prefers account-cache market data, reducing mistakes from new symbol prefixes.
Low user-visible impact; users on v1.4.58 can upgrade as needed.

v1.4.58 · 2026-04-22 — ✨ MCP push, idempotency, and error semantics¶

MCP supports real-time order and fill pushes, reducing polling.
REST, CLI, and MCP trade-write endpoints support idempotency keys to reduce duplicate-submit risk after network retries.
MCP error semantics are more consistent for clients.

v1.4.57 · 2026-04-22 — 🔴 Account, quote, and trade fixes¶

Fixed routing issues across multi-account, multi-broker, and quote-query scenarios.
SMS verification supports one-shot callbacks for automation.
Order, funds, positions, cash-log, and history-query errors are clearer.

v1.4.56 · 2026-04-21 — 🔴 US futures routing¶

US futures order and query routing was fixed.
Futures users should upgrade.

v1.4.55 · 2026-04-21 — 🔴 Futures market and fill fixes¶

Futures exchange_str, market-state, and multi-market queries were fixed.
HK and US futures users should upgrade.

v1.4.54 · 2026-04-21 — 🔴 HK futures order routing¶

HK futures order routing was fixed.
HK futures trading users should upgrade.

v1.4.53 · 2026-04-21 — 🟡 Sim trading, conditional orders, and option symbol conversion¶

Sim-account positions, funds, and max-trade-quantity queries were fixed.
Conditional orders were added.
Option symbols can be converted between Futu and OCC formats.

v1.4.52 · 2026-04-21 — 🟡 Verification fixes and checks¶

Fixed sim-account, REST error, and input-validation issues.
Release checks became stricter.
Users on v1.4.51 can upgrade as needed.

v1.4.51 · 2026-04-21 — 🔴 `US.AAPL` order-format fix¶

Users migrating from the official SDK or placing orders through MCP agents should upgrade.

REST, CLI, MCP, and native entry points accept market-prefixed symbols for order placement.
Invalid trd_env, nonexistent account, and empty-list inputs return clearer errors.

v1.4.50 · 2026-04-21 — 🔄 Market-ID coverage and checks¶

Market-ID coverage was expanded.
Local checks help prevent future market omissions.
User-visible behavior is largely unchanged.

v1.4.49 · 2026-04-21 — 🔄 Architecture cleanup¶

Removed obsolete trade-unlock compatibility code.
Release automation was improved.
Users on v1.4.48 can skip it.

v1.4.48 · 2026-04-21 — 🔴 Broker routing fixes¶

Trade queries and write requests select routes by the account's broker.
Fixes route selection for multi-broker accounts in cross-market scenarios.

v1.4.47 · 2026-04-21 — 🔴 Broker routing and global state¶

Fixed trade routing for multi-broker accounts.
/api/global-state market status is more accurate.
Multi-account and multi-market users should upgrade.

v1.4.46 · 2026-04-20 — 🟢 Query defenses and option fields¶

Cache-read endpoints return errors for invalid input instead of disguising it as empty data.
Option snapshots include more fields.

v1.4.45 · 2026-04-20 — 🔴 REST field-name compatibility¶

REST request bodies accept official-SDK-style camelCase field names.
History-order and history-fill endpoints no longer silently use defaults when field names differ.

v1.4.44 · 2026-04-20 — 🔴 Protocol field completeness¶

Order, position, funds, fill, and quote responses include more complete fields.
Response shapes are closer to the official SDK.
Recommended for clients that rely on full response fields.

v1.4.43 · 2026-04-20 — 🔴 History orders and fills¶

Multi-market authorized accounts now send the correct market filters for history orders and fills.
Strict-permission accounts no longer return empty history data.

v1.4.42 · 2026-04-20 — 🟢 Option-position fields and polish¶

Option positions include DTE.
Several non-blocking feedback items were cleaned up.

v1.4.41 · 2026-04-20 — 🔴 Regression fixes¶

Fixed issues in order placement, conditional orders, account isolation, history queries, and quote hints.
Recommended for v1.4.39-v1.4.40 users.

v1.4.40 · 2026-04-20 — 🟡 Index aliases and reconfirm order¶

HK index ticker aliases work for quote queries.
Added /api/reconfirm-order.
Market-parameter docs and errors are clearer.

v1.4.39 · 2026-04-20 — 🔴 Option and history-query hotfixes¶

Fixed option-chain, history-order, history-fill, and max-trade-quantity queries.
CLI and MCP trade-write endpoints gained idempotency parameters.

v1.4.38 · 2026-04-20 — 🔴 Options, idempotency, and real-time push¶

Option chain, option snapshot, and history queries work for 2FA accounts.
REST, CLI, MCP, and native entry points support order idempotency.
MCP adds real-time order and fill push.

v1.4.37 · 2026-04-19 — 🟢 UX polish¶

CLI, docs, and error hints were polished.
Low-risk maintenance release; users on v1.4.36 can skip it.

v1.4.36 · 2026-04-19 — 🛠 Whitelist and market-closed hint fixes¶

Account-whitelist rejection returns 403 instead of rate-limit style errors.
Market-closed hints are generated for the actual market.
Fixed a funds-query whitelist bypass.

v1.4.35 · 2026-04-19 — 🏷️ Market-closed hints and API-key account whitelist¶

futucli gen-key can restrict each key to selected accounts, markets, and symbols.
Order failures include clearer market-closed hints.
Useful for multi-agent or shared-daemon deployments.

v1.4.34 · 2026-04-19 — 🔴 2FA place-order fix¶

Fixed 2FA accounts that were unlocked but still could not place orders.
Improved moomoo-token and unlock-failure hints.
REST, CLI, gRPC, and MCP show errors more consistently.

v1.4.33 · 2026-04-19 — Per-broker trade unlock¶

unlock-trade can target a specific broker.
Hidden or problematic sub-accounts no longer block other broker accounts.

v1.4.32 · 2026-04-18 — Daemon management commands¶

Added status, reload, and shutdown management commands.
Management endpoints show clearer warnings in security mode.

v1.4.31 · 2026-04-18 — 🔴 Trade unlock rewrite¶

Trade unlock runs per broker and in parallel.
One failing sub-account no longer blocks other accounts.
Unlock responses include per-account success or failure reasons.

v1.4.30 · 2026-04-18 — 🎯 Official Python SDK capability coverage¶

REST, CLI, and MCP completed the main user-facing methods from the official Python SDK.
Added cash log, capital flow, K-line, option chain, max trade quantity, and related query capabilities.
Docs and examples were updated.

v1.4.29 · 2026-04-18¶

Fixed simulated-account funds queries.
Added /readyz.
Startup logs are quieter.

v1.4.28 · 2026-04-18¶

More simulated-account and trading-error hint fixes.
Runtime dependencies and docs were updated.

v1.4.27 · 2026-04-18¶

Account list, positions, and orders use more reliable account routing.
CLI account tables show more key fields.
MCP gained more quote and trade tools.

v1.4.26 · 2026-04-17¶

Fixed account-list gaps caused by broker connection address selection.
Broker addresses now prefer server-provided configuration.
Multi-platform login and account queries are more stable.

v1.4.25 · 2026-04-17¶

Broker-list changes refresh the valid broker list automatically.
setup-only mode is faster.
Server-time adjustment and connection configuration are more robust.

v1.4.24 · 2026-04-17¶

Fixed overseas-account connection identification.
Login configuration accepts more response shapes.
Error hints are clearer.

v1.4.23 · 2026-04-17¶

Dynamic connection configuration has higher priority.
One-time password and login-signature handling are more stable.
Startup connection success rate improved.

v1.4.22 · 2026-04-17¶

Platform connection addresses support DNS fallback.
CLI can store login passwords securely.
Login command errors are clearer.

v1.4.21 · 2026-04-17¶

Device-ID lifecycle was redesigned.
Recovery after login failure is more reliable.
Recommended for long-running daemon users.

v1.4.20 · 2026-04-17¶

Login pipeline edge cases were fixed.
Connection retry and error hints are more stable.

v1.4.19 · 2026-04-17¶

Continued login, connection, and account-discovery fixes.
User-facing APIs are largely unchanged.

v1.4.18 · 2026-04-17¶

CLI and configuration examples were updated.
Login and startup experience improved slightly.

v1.4.17 · 2026-04-17¶

Login stability improved further.
Recommended for users seeing SMS or device-verification issues.

Fixed login pipeline, platform selection, device identity, SMS verification, and connection retry issues across several quick releases.
Added --platform <futunn|moomoo> to distinguish accounts sharing the same phone number across platforms.
Overseas accounts no longer use an unsuitable connection pool.

v1.4.10 · 2026-04-16¶

Account list, positions, and orders use a more stable account channel.
Account data after login is more complete.

v1.4.8-v1.4.9 · 2026-04-16¶

Early login and connection stability fixes.
Foundation work for account, quote, and trading APIs.

v1.0-v1.4.7¶

These versions were mostly maintenance refactors and protocol alignment. If you are upgrading from an early version, use the latest release.