Production usage
Reuse clients and use the same account type and live/demo settings for REST and WebSockets. Keep credentials server-side with minimum permissions, synchronize time, use IP restrictions where supported and rotate keys regularly.
Set timeouts and bound concurrency
Set an HTTP timeout for each operation and limit concurrent requests across workers. See Configuration for client options.
Retry reads deliberately
Retry transient read failures with a maximum attempt count or deadline, exponential backoff and jitter. Respect server retry guidance. Correct invalid parameters, permissions and signatures before retrying.
Bitget limits differ by endpoint, product and account. Budget startup and recovery traffic separately from normal commands. Check whether limits apply per account, IP or endpoint, and whether REST and WebSocket requests share them. Paginate history and open-order reads.
Keep account state up to date
Use REST to submit orders and private WebSocket subscriptions to follow what happens next. Order, fill, balance and position events update your application's account state as changes occur.
- Connect the private streams and watch for subscription acknowledgements or errors before submitting orders. Load any starting state the streams do not provide, and account for events received while that data loads.
- Submit the order through REST. Save the returned IDs and inspect the response for errors or immediate results. An acknowledgement alone does not establish the order's later state.
- Apply matching WebSocket events to local state. Use order and fill events to track execution, and balance or position updates for the account changes your application needs. These events can arrive separately.
- Use REST to fill a specific gap: startup data, updates missed during a disconnect, conflicting events, or an outcome that neither the response nor the stream has resolved. Once account state is current, continue applying WebSocket updates.
Do not query REST after every submission or poll it while the required streams are healthy and complete. A quiet stream can mean nothing has changed. Check connection and subscription health separately from account activity.
Trigger follow-up work from position changes
Where the exchange and market provide position updates, they are useful triggers for follow-up logic. For example, when a position opens or increases, use its updated size to place or adjust stop-loss and take-profit (SL/TP) orders. Compare the previous and current position state; receiving another position message does not necessarily mean the position changed.
For signed position sizes, compare absolute exposure within the same direction and handle a direction change separately. Also resize or cancel obsolete protection when exposure shrinks or the position closes.
Debounce bursts of partial-fill updates to reduce API calls, and set a maximum wait so continuous updates cannot postpone adjustments indefinitely. Choose the debounce delay and maximum wait to fit the exchange's rate limits and the delay your strategy can tolerate.
When applying an adjustment:
- Check stream health and use the latest reconciled position and order state.
- Process changes for the same position sequentially and skip adjustments that are already satisfied.
- Pause dependent adjustments while recovering account state.
- Include the account, market and position side in state keys where applicable.
Recover after a connection gap
Use the SDK's reconnect lifecycle events to mark affected state as stale when connection recovery starts and to trigger REST reconciliation when the socket reopens. The event names differ by SDK; see the recovery section below. A reopened socket does not prove that authentication, subscriptions or account-state recovery are complete.
Confirm the required streams are healthy, load any missed order, fill, balance or position state, and account for updates received during those reads. Then compare current positions and open orders with the intended state and create, amend or cancel orders only where needed, including SL/TP orders. Resolve uncertain requests before submitting replacements so recovery does not create duplicates. Resume dependent actions once their required state is current.
See Account State for the full workflow. The private stream guide shows how to receive updates; the examples print events rather than maintain a complete account-state store.
Bitget recovery events
Use reconnect and unexpected closure to mark affected state stale. The SDK reconnects, authenticates and restores subscriptions automatically. Use reconnected to start recovering missed account updates; it signals an open socket, not completed account-state recovery. Buffer live events during recovery and use saved identifiers to remove duplicates.
Classic Spot uses V2 balances, open orders, history and fills. UTA uses V3 equivalents, including getTradeFills() for private executions. getFills() is public market data. Do not assume subscriptions replay every missed event. See Private account updates.
Keep order, execution, balance and position state separate. Scope state by account, environment, category and symbol, with position side where relevant. Spot amounts and futures quantities are not interchangeable. Maintain decimal precision throughout validation and accounting.
Shut down cleanly
Stop accepting new work, record or resolve in-flight outcomes and save order identifiers and recovery checkpoints. Then call closeAll() on subscription clients and getWSClient().closeAll() on WebSocket API clients. Clear application-owned timers and listeners.
Closing a process or connection does not cancel exchange orders. Cancelling an order is a separate command, and cancellation cannot reverse a fill.
Logging
Log selected operation names, sanitized codes, durations, reconnects and recovery results. Whole error and request objects can contain API keys or other private data even when some credentials have been redacted. Keep account payloads out of public logs.
Upgrading
Review release notes and run integration checks before upgrading. Commit the lockfile to reproduce deployed versions.
After upgrades, check support for your account type, endpoints and demo environment, along with any changes to batch response types. Test account permissions and order handling separately from bundling and public connectivity.