Bybit Pre Check Order API：风险限额就绪清单
已验证事实边界
1. Bybit publishes official documentation for a V5 pre-check-order route. 2. Bybit publishes official V5 create-order documentation. 3. Bybit publishes official instruments-info documentation. 4. A pre-check response is different from a live order response. 5. Instrument metadata is part of a safe order validation record because it shapes size, price and market assumptions. 6. The public documentation does not prove future acceptance, fill result, account risk limit, liquidation handling or support outcome.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Source chain | pre-check belongs after instrument metadata and before live placement | store the metadata snapshot, request body and pre-check result together | a later private risk state may differ from the pre-check state |
| Live order gap | pre-check and live order placement are separate endpoint outcomes | never mark an order placed until the live place-order response is recorded | market movement and account changes can occur between check and placement |
| Risk-limit context | instrument and account constraints shape valid order size | record symbol, category, limit fields and account mode before acting | public docs cannot disclose a private account's current risk tier |
| Retry discipline | blind retry can create duplicate or inconsistent evidence | use client ids and stop rules before repeating any live order action | network errors may hide server-side results until reconciled |
| Reporting boundary | a successful pre-check is a readiness signal, not a performance claim | report it as validation evidence only, not as fill certainty or safety proof | future venue behavior and support handling remain unknown |
来源地图
- Bybit：V5 API: Pre Check Order（bybit-pre-check-order）
- Bybit：V5 API: Place Order（bybit-create-order）
- Bybit：V5 API: Get Instruments Info（bybit-instruments-info）
- Bybit：V5 API introduction（bybit-docs-root）
控制说明
1. Source chain
这一项要求读者把公开来源翻译成操作规则。这里的含义是：pre-check belongs after instrument metadata and before live placement。可执行动作是：store the metadata snapshot, request body and pre-check result together。仍然未知的是：a later private risk state may differ from the pre-check state。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Live order gap
这里的含义是：pre-check and live order placement are separate endpoint outcomes。可执行动作是：never mark an order placed until the live place-order response is recorded。仍然未知的是：market movement and account changes can occur between check and placement。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Risk-limit context
这里的含义是：instrument and account constraints shape valid order size。可执行动作是：record symbol, category, limit fields and account mode before acting。仍然未知的是：public docs cannot disclose a private account's current risk tier。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Retry discipline
这里的含义是：blind retry can create duplicate or inconsistent evidence。可执行动作是：use client ids and stop rules before repeating any live order action。仍然未知的是：network errors may hide server-side results until reconciled。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Reporting boundary
这里的含义是：a successful pre-check is a readiness signal, not a performance claim。可执行动作是：report it as validation evidence only, not as fill certainty or safety proof。仍然未知的是：future venue behavior and support handling remain unknown。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- a later private risk state may differ from the pre-check state
- market movement and account changes can occur between check and placement
- public docs cannot disclose a private account's current risk tier
- network errors may hide server-side results until reconciled
- future venue behavior and support handling remain unknown
实用结论
Bybit V5 pre-check 路径只有放在更大的证据链中才有价值。来源支撑的证据链应包括 instrument metadata、本地订单构造、pre-check response、真实 place-order response 和事后对账。pre-check 可以减少可避免拒单，但不能被报告成真实订单一定被接受、成交、不会触发风险，或在私人账户例外下会获得支持的保证。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相关专题与工具:交易所 API 与行情数据核查