Diagnose by failure class
Use this page when you already know something is wrong and need the fastest public recovery route.Signature and encryption failures
- Verify signer identity recovery matches trader.
- Verify payload bytes are unchanged between signing and encryption.
- Verify operator encryption key fetch succeeds before submission.
- Recheck Request Signing Reference and Request Encryption Reference before retrying.
Safety failures
- Map safety-failure variant from response.
- Check tick-size, minimum-size, notional, market support, and collateral constraints.
- Rebuild, resign, and re-encrypt request.
- Use Trading Safeties and Guards and Margin Requirements when the failure is really a risk-constraint issue rather than malformed input.
Sequencing versus execution confusion
- Treat receipt as sequencing acknowledgment only.
- Track
ORDER_UPDATEand account updates for outcome. - Reconcile with REST snapshot after reconnect.
Realtime reconnect instability
- Reconnect WebSocket.
- Resubscribe feeds with explicit filters.
- Re-bootstrap state from REST.
- Recheck Realtime Connection Model if the issue repeats.
Escalate by symptom
| Symptom | Best next route |
|---|---|
| bad signature, bad nonce, or request-rejection uncertainty | How to Handle API Errors and Recovery and Error Reference |
| lifecycle mismatch after receipt | How to Handle Order Sequencing vs Execution and Order and Account Event Reference |
| repeated docs mismatch or unresolved public ambiguity | Support Channels |
| KYC or Blockpass-specific failure | Support Channels and then Blockpass support if the public docs do not resolve it |