使用MQL5和Python集成经纪商API与智能交易系统·综合运用
（3/3）·从 WebSocket 桥接到资金管理 EA，把账户余额阈值触发入金跑通全流程
从命令行到MT5：打通脚本与EA的联调验证
先用 Notepad++ 直接拉起命令提示符（cmd），好处是路径自动落在 deriv_api_handler.py 所在目录，不用手动 cd。敲 python deriv_api_handler.py 后，若没填有效 API 令牌和应用 ID，会立刻收到握手 401 与 {"error":"InvalidAppID"}；换成真实凭据才能进授权并去公共文件夹找 mql5_to_python.txt 命令文件。
EA 侧用 10,000 本金的模拟账户测，我把余额阈值设成 100,000，低于它就触发一次入金指令。MT5 工具箱「智能交易」日志里能看到：2025.01.14 11:49:56.012 余额 10000.22，判定低于阈值后写命令文件并拉起 Python，约 5 秒后回读 python_to_mql5.txt。
本例返回的是 PermissionDenied（需 payments 权限域），因演示用了随机凭据。真实令牌若带对应 scope，链路会生成含 API 响应的回传文件，EA 与脚本、API 三者即算联通。外汇/贵金属模拟环境联调虽无本金风险，但权限域配错会直接卡在授权环节。
别把随机凭据当通解
演示日志里的 CR4000128、MTR130002534 都是脱敏占位，直接抄进自己脚本只会持续吃 401。去 Deriv 后台开好 app_id 并勾选 payment 类 scope，再跑联调才有效。
python deriv_api_handler.py Error during authorization: Handshake status class="num">401 Unauthorized -+-+- {&class="macro">#x27;date&class="macro">#x27;: &class="macro">#x27;Thu, class="num">15 Jan class="num">2025 class="num">08:class="num">43:class="num">53 GMT&class="macro">#x27;, &class="macro">#x27;content-type&class="macro">#x27;: &class="macro">#x27;application/json;charset=UTF-class="num">8&class="macro">#x27;, &class="macro">#x27;content-length&class="macro">#x27;: &class="macro">#x27;class="num">24&class="macro">#x27;, &class="macro">#x27;connection&class="macro">#x27;: &class="macro">#x27;keep-alive&class="macro">#x27;, &class="macro">#x27;content-language&class="macro">#x27;: &class="macro">#x27;en&class="macro">#x27;, &class="macro">#x27;upgrade&class="macro">#x27;: &class="macro">#x27;websocket&class="macro">#x27;, &class="macro">#x27;sec-websocket-accept&class="macro">#x27;: &class="macro">#x27;yfwlFELh2d3KczdgV3OT8Nolp0Q=&class="macro">#x27;, &class="macro">#x27;cf-cache-status&class="macro">#x27;: &class="macro">#x27;DYNAMIC&class="macro">#x27;, &class="macro">#x27;server&class="macro">#x27;: &class="macro">#x27;cloudflare&class="macro">#x27;, &class="macro">#x27;cf-ray&class="macro">#x27;: &class="macro">#x27;902cd20129b638df-HRE&class="macro">#x27;, &class="macro">#x27;alt-svc&class="macro">#x27;: &class="macro">#x27;h3=":class="num">443"; ma=class="num">86400&class="macro">#x27;} -+-+- b&class="macro">#x27;{"error":"InvalidAppID"}&class="macro">#x27; Failed to authorize. 退出。 已连接并已授权。正在等待命令… Checking for command file at: C:/Users/YourComputerName/AppData/Roaming/MetaQuotes/Terminal/Common/Files/mql5_to_python.txt Command file found: C:/Users/YourComputerName/AppData/Roaming/MetaQuotes/Terminal/Common/Files/mql5_to_python.txt Raw Command read: &class="macro">#x27;{"mt5_deposit": class="num">1, "amount": class="num">100000.00, "from_binary": "CR4000128", "req_id": class="num">1, "to_mt5": "MTR130002534"}&class="macro">#x27; Processed Command: &class="macro">#x27;{"mt5_deposit": class="num">1, "amount": class="num">100000.00, "from_binary": "CR4000128", "req_id": class="num">1, "to_mt5": "MTR130002534"}&class="macro">#x27; Processing command: {"mt5_deposit": class="num">1, "amount": class="num">100000.00, "from_binary": "CR4000128", "req_id": class="num">1, "to_mt5": "MTR130002534"} Response: {&class="macro">#x27;echo_req&class="macro">#x27;: {&class="macro">#x27;amount&class="macro">#x27;: class="num">100000, &class="macro">#x27;from_binary&class="macro">#x27;: &class="macro">#x27;CR4000128&class="macro">#x27;, &class="macro">#x27;mt5_deposit&class="macro">#x27;: class="num">1, &class="macro">#x27;to_mt5&class="macro">#x27;: &class="macro">#x27;MTR130002534&class="macro">#x27;}, &class="macro">#x27;error&class="macro">#x27;: {&class="macro">#x27;code&class="macro">#x27;: &class="macro">#x27;PermissionDenied&class="macro">#x27;, &class="macro">#x27;message&class="macro">#x27;: &class="macro">#x27;Permission denied, requires payments scope(s).&class="macro">#x27;}, &class="macro">#x27;msg_type&class="macro">#x27;: &class="macro">#x27;mt5_deposit&class="macro">#x27;} Response written. 退出循环。 class="num">2025.01.class="num">14 class="num">11:class="num">49:class="num">56.012 Fund Manager EA1(EURUSD,M1) Current Account Balance: class="num">10000.22 class="num">2025.01.class="num">14 class="num">11:class="num">49:class="num">56.012 Fund Manager EA1(EURUSD,M1) Balance is below the threshold. Attempting a deposit... class="num">2025.01.class="num">14 class="num">11:class="num">49:class="num">56.013 Fund Manager EA1(EURUSD,M1) Deposit command written to file: C:\Users\BTA24\AppData\Roaming\MetaQuotes\Terminal\Common\Files\mql5_to_python.txt class="num">2025.01.class="num">14 class="num">11:class="num">49:class="num">56.097 Fund Manager EA1(EURUSD,M1) Python script launched successfully. class="num">2025.01.class="num">14 class="num">11:class="num">50:class="num">01.132 Fund Manager EA1(EURUSD,M1) Response file path: C:\Users\BTA24\AppData\Roaming\MetaQuotes\Terminal\Common\Files\python_to_mql5.txt
「跨账户注资被拒的日志现场」
在 EURUSD M1 周期下跑 Fund Manager EA1，2025.01.14 11:50:01.133 打出一条来自 Python 端的回执：尝试从 binary 账户 CR4000128 向 MT5 账户 MTR130002534 划转 100000 单位、mt5_deposit 标志置 1，msg_type 为 mt5_deposit。 该请求直接返回 error.code = PermissionDenied，附带 message 指明「requires payments scope(s)」，随后 EA 在日志里补了一句 Deposit failed，把完整 echo_req 与 error 复写一遍。 这类报错不是行情或点差问题，而是 API 令牌缺少 payments 权限域。开 MT5 把 EA 用的 token 拿到 Deriv 后台比对 scope 列表，缺 payments 就补授权，否则任何跨账户调拨都会卡在同一行日志。 外汇与贵金属跨账户操作本身属高风险动作，权限误配还会放大资金误转概率，验证前先在模拟环境跑通再上真仓。
class="num">2025.01.class="num">14 class="num">11:class="num">50:class="num">01.133 Fund Manager EA1(EURUSD,M1) Response from Python: {"echo_req": {"amount": class="num">100000, "from_binary": "CR4000128", "mt5_deposit": class="num">1, "to_mt5": "MTR130002534"}, "error": {"code": "PermissionDenied", "message": "Permission denied, requires payments scope(s)."}, "msg_type": "mt5_deposit"} class="num">2025.01.class="num">14 class="num">11:class="num">50:class="num">01.133 Fund Manager EA1(EURUSD,M1) Deposit failed. Response: {"echo_req": {"amount": class="num">100000, "from_binary": "CR4000128", "mt5_deposit": class="num">1, "to_mt5": "MTR130002534"}, "error": {"code": "PermissionDenied", "message": "Permission denied, requires payments scope(s)."}, "msg_type": "mt5_deposit"}
◍ 画得少，看得清
把 MQL5 的 EA 与券商外部 API 打通后，资金耗尽这种托管 VPS 上最烦人的意外，就能靠阈值自动充值化解。演示里用的是空账户跑通 Deriv 的接口回包，证明链路本身可行，附件里 3.82 KB 的 Python 脚本与 5.13 KB 的 EA 文件可直接下到 MT5 里改阈值验证。 评论区有人点破：MQL5 自带 WebSocket 和 REST 调用，多数场景根本不需要绕一层 Python；这条提醒值得你在开搞前先掂量，别为了「集成」而集成。外汇与贵金属杠杆高，自动补钱只是防掉线，不替你扛回撤风险。 真要落地，先把 Fund_Manager_EA 里的余额判定参数调到你能接受的下限，挂模拟账户跑几天看 API 响应延迟，再决定要不要加出金逻辑。