API 执行控制雷达：订单预览、验证与改单确认

NexuAlpha 直接答案：Exchange API order-control words are not interchangeable. Coinbase documentation exposes Advanced Trade API order management and user-facing preview flows. Kraken's Advanced API FAQ says AddOrder or addOrder can use the validate parameter to simulate order details without returning an order ID. OKX documentation says successful amend responses only mean the request has been accepted and users should refer to WebSocket order results for the amendment outcome. Binance Spot documentation exposes test-order surfaces for validating order parameters. NexuAlpha Radar therefore treats preview, validate, test, acknowledgement and final execution as separate states that must be reconciled.

决策结果：For any bot or API workflow, log the client order ID, dry-run or preview result, exchange acknowledgement, final order status, WebSocket reconciliation, cancel or amend result and retry idempotency policy separately. Stop if an accepted request is being treated as a fill, a validation response is treated as a live order, or a lost response can duplicate an order.

证据快照。本文在 2026-09-26T20:44:49.316Z 读取 Coinbase Developer Platform、Kraken Support、OKX、Binance Developer Docs。本地队列、旧草稿、搜索摘要、社交转述、价格图或 AI 摘要都不被当作事实证明。它们最多提示问题，不能替代公开来源列表与主张映射。

核验事实。主张 c1：Coinbase Developer Platform describes Advanced Trade API as supporting programmatic trading and order management through REST API and WebSocket protocol. 主张 c2：Kraken says the validate input parameter for REST AddOrder or WebSocket addOrder simulates order checks and a validate call never returns an order ID. 主张 c3：OKX documentation says a successful order-amend response means the request was accepted and users should refer to WebSocket order results for the amendment outcome. 主张 c4：Binance Developer Docs present Spot REST API endpoint definitions, request parameters, payload schemas, endpoint security types and rate-limit information for authenticated trading workflows.这些事实刻意保持窄口径，不证明个人资格、未来可用性、执行质量、超出原文的法律状态、税务处理、账户批准、客服结果、赎回成功、价格方向、流动性深度或平台偿付能力。

围绕 order preview validate amend acknowledgement API execution controls radar 的决策纪律，不是寻找绝对赢家，而是建立来源绑定的评分卡：哪个官方来源回答了当前问题，哪个控制项仍为空白，哪个空白会改变用户风险，哪个测试可逆，哪个条件会重开决策。诚实的空白比编造优势更安全。

FAQ。短答案是什么？Exchange API order-control words are not interchangeable. 首先核验什么？核验官方来源和准确控制表面。不能推断什么？不能推断资格、未来支持、法律处理、税务处理、恢复、执行质量、流动性、赎回、消费者保护或账户批准。何时停止？当来源、对象、用户状态、权限、路径、发行人、司法辖区或故障处理不清楚时停止。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。