OKX Chase Limit Trigger Orders：API 就绪清单
已验证事实边界
1. OKX changelog documents chase as a post-trigger execution type for FUTURES/SWAP trigger orders. 2. OKX changelog describes advChaseParams for placement and amendment flows. 3. OKX changelog describes subAlgoIdList as a read-side field for spawned chase order identifiers after trigger firing. 4. OKX official API documentation contains separate place-algo-order, amend-algo-order and algo orders channel surfaces. 5. A chase trigger order requires both write-route validation and read-route reconciliation; a placement response alone is not a final execution record. 6. The source set does not prove private account eligibility, market acceptance, fill quality, liquidation behavior, support outcome or future availability.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Route coverage | place, amend, details, lists, history and websocket reads may all need chase-aware handling | mark every affected endpoint before releasing an SDK or bot update | whether a private integration uses every route consistently |
| Parameter boundary | chase distance, maximum chase distance and trigger state have distinct validation rules | reject mixed or undocumented parameter combinations before sending live requests | future parameter changes in OKX docs remain outside this snapshot |
| Spawned identifier | the order that exists after trigger firing may be represented by a spawned algo identifier | store parent algo id, spawned id, trigger time and channel update separately | whether final fill and position records reconcile without gaps |
| Failure wording | users can confuse a chase setup failure with ordinary order rejection | write explicit labels for pre-trigger amend, trigger fire, spawned order and final fill states | support diagnosis for private failures remains account-specific |
| Production stop rule | new order semantics deserve a reversible deployment path | stop if demo, dry run, route coverage, channel reconciliation or rollback criteria are missing | public documentation cannot prove future product availability or private risk-limit state |
来源地图
- OKX：OKX API Changelog（okx-api-changelog）
- OKX：Place algo order（okx-place-algo-order）
- OKX：Amend algo order（okx-amend-algo-order）
- OKX：Algo orders channel（okx-algo-orders-channel）
控制说明
1. Route coverage
这一项要求读者把公开来源翻译成操作规则。这里的含义是：place, amend, details, lists, history and websocket reads may all need chase-aware handling。可执行动作是：mark every affected endpoint before releasing an SDK or bot update。仍然未知的是：whether a private integration uses every route consistently。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Parameter boundary
这里的含义是：chase distance, maximum chase distance and trigger state have distinct validation rules。可执行动作是：reject mixed or undocumented parameter combinations before sending live requests。仍然未知的是：future parameter changes in OKX docs remain outside this snapshot。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Spawned identifier
这里的含义是：the order that exists after trigger firing may be represented by a spawned algo identifier。可执行动作是：store parent algo id, spawned id, trigger time and channel update separately。仍然未知的是：whether final fill and position records reconcile without gaps。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Failure wording
这里的含义是：users can confuse a chase setup failure with ordinary order rejection。可执行动作是：write explicit labels for pre-trigger amend, trigger fire, spawned order and final fill states。仍然未知的是：support diagnosis for private failures remains account-specific。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Production stop rule
这里的含义是：new order semantics deserve a reversible deployment path。可执行动作是：stop if demo, dry run, route coverage, channel reconciliation or rollback criteria are missing。仍然未知的是：public documentation cannot prove future product availability or private risk-limit state。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether a private integration uses every route consistently
- future parameter changes in OKX docs remain outside this snapshot
- whether final fill and position records reconcile without gaps
- support diagnosis for private failures remains account-specific
- public documentation cannot prove future product availability or private risk-limit state
实用结论
OKX 的 chase limit order 更新应被当作 API 就绪变更，而不是交易信号。OKX changelog 说明 FUTURES 与 SWAP trigger orders 可以把 chase 作为 post-trigger execution type，并在下单或 amend 流程中使用 advChaseParams，在触发后由 read endpoints 返回 subAlgoIdList。因此安全的实现清单需要覆盖 route、参数校验、pre-trigger amend 规则、spawned-order reconciliation、面向用户的失败标签和账户级 dry run，然后才进入生产。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相关专题与工具:交易所 API 与行情数据核查
来源与证据
04- OKX API Changelog · okx.com
- Place algo order · okx.com
- Amend algo order · okx.com
- Algo orders channel · okx.com