Skip to main content

API Reliability and Recovery

Reliable clients preserve request identity, separate admission from terminal execution, and prove that reads cover the event they depend on. This page links the detailed contracts for those decisions.

Candidate availability

The account-freshness fields, bounded delegated-idempotency maintenance, narrow MM pre-admission recovery fix, and centralized private-WebSocket authorization described here are candidate changes. They are not production guarantees until the backend is deployed and authenticated public/customer-lane readback passes. The documentation site may publish before that backend release.

Choose the evidence you need

QuestionReadRequired evidence
Can this account view size the next order?Account freshness and reconciliationSnapshot batch, independent authority head, lag/status, and coverage of the terminal event.
May I retry this HTTP mutation?IdempotencyThe identical operation and idempotency identity, or proof the first attempt was not submitted.
Did an MM cancel/replace finish?BSL rejects and recoveryPre-admission failure proof, or terminal receipt/execution reconciliation after uncertain admission.
Can this private token still subscribe?Private WebSocket channelsCurrent scope, engine-account mapping, credential ownership, and revocation state.
How do I recover a timeout or disconnect?Troubleshooting and WebSocket reconnectStable code/request id, preserved cursor and request identity, then REST/receipt reconciliation when required.

An HTTP 202, gateway ACK, or COMMAND ACK confirms a stage of processing. It does not replace terminal order, fill, cancel, or reject evidence. A timeout or lost response does not prove rejection; reconcile the original identity before creating a new order.

Design references

The candidate review compared these contracts with official exchange guidance on ambiguous submissions, client identifiers, rate limits, key permissions, and sequence recovery. These links are references for client design, not a ranking or a claim of feature or performance parity:

For current SentiCore availability, always check Status and Availability.