交易所 API Changelog 雷达：签名、版本与订单语义披露
已验证事实边界
1. Binance developer introduction says official supported interfaces are documented in its portal and product-specific updates should be reviewed before deployment or upgrade. 2. Binance spot block matching change log includes a time-sensitive signed-endpoint notice about percent-encoding payloads before computing signatures. 3. Binance margin trading change log includes 2026 changes for margin order endpoints and sideEffectType behavior. 4. OKX API changelog includes order-semantics updates such as chase trigger order parameters and spawned order identifiers. 5. A changelog entry can change signing logic, request weights, endpoint semantics, read-side reconciliation or user-facing error handling. 6. A public changelog cannot prove a private integration has migrated, tested, rolled back or survived production traffic.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Effective date | some API changes have a stated future or effective date and others are documentation updates | record the date, timezone and first production window separately | whether a venue delays, revises or rolls back the change |
| Signing rule | signature construction changes can break otherwise valid requests | test canonical payload generation with fixtures before sending signed endpoints | whether all internal SDKs share the same encoding behavior |
| Endpoint semantics | an endpoint can gain new side effects, weights or order states without changing its high-level product label | map endpoint, request fields, response fields and account surface | private account restrictions and region-specific availability |
| Reconciliation | read endpoints and websocket channels may need new identifiers or state labels | update database schema, event parser and alert copy with non-secret identifiers | whether historical records can be backfilled cleanly |
| Stop condition | a changelog is not migrated until tests and rollback evidence exist | stop deployment if source URL, date, fixture, parser update or rollback path is missing | future undocumented behavior remains outside the official evidence boundary |
来源地图
- Binance Developers：Binance Developer Documentation Introduction（binance-developer-intro）
- Binance Developers：Spot Block Matching Change Log（binance-block-match-changelog）
- Binance Developers：Margin Trading API Change Log（binance-margin-changelog）
- OKX：OKX API Changelog（okx-api-changelog）
控制说明
1. Effective date
这一项要求读者把公开来源翻译成操作规则。这里的含义是：some API changes have a stated future or effective date and others are documentation updates。可执行动作是：record the date, timezone and first production window separately。仍然未知的是：whether a venue delays, revises or rolls back the change。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Signing rule
这里的含义是：signature construction changes can break otherwise valid requests。可执行动作是：test canonical payload generation with fixtures before sending signed endpoints。仍然未知的是：whether all internal SDKs share the same encoding behavior。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Endpoint semantics
这里的含义是：an endpoint can gain new side effects, weights or order states without changing its high-level product label。可执行动作是：map endpoint, request fields, response fields and account surface。仍然未知的是：private account restrictions and region-specific availability。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Reconciliation
这里的含义是：read endpoints and websocket channels may need new identifiers or state labels。可执行动作是：update database schema, event parser and alert copy with non-secret identifiers。仍然未知的是：whether historical records can be backfilled cleanly。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Stop condition
这里的含义是：a changelog is not migrated until tests and rollback evidence exist。可执行动作是：stop deployment if source URL, date, fixture, parser update or rollback path is missing。仍然未知的是：future undocumented behavior remains outside the official evidence boundary。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether a venue delays, revises or rolls back the change
- whether all internal SDKs share the same encoding behavior
- private account restrictions and region-specific availability
- whether historical records can be backfilled cleanly
- future undocumented behavior remains outside the official evidence boundary
实用结论
交易所 API changelog 不是发布说明装饰，而是操作控制。Binance developer material 说明部署或升级前应查看依赖产品的文档和更新，其 block-matching 与 margin changelog 包含 signed-endpoint 和 order endpoint 变更；OKX API changelog 则记录了 chase trigger orders 与 spawned order identifiers 等新订单语义。雷达决策是把每条 changelog 当成 source-mapped migration object，记录 effective date、endpoint、signing rule、affected account surface、rollback path 和 private-test evidence。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相关专题与工具:交易所 API 与行情数据核查
来源与证据
04- Binance Developer Documentation Introduction · developers.binance.com
- Spot Block Matching Change Log · developers.binance.com
- Margin Trading API Change Log · developers.binance.com
- OKX API Changelog · okx.com