Account streams

Read the account snapshot, open positions and live open orders once for the account bound to the approved key. Mint a realtime ticket, authenticate the socket, wait for auth_ok and subscribe with its accountId. Keep data associated with both account and environment, and clear that association when the active identity changes.

GET /v1/accounts/{accountId}/orders/open returns live working orders. GET /v1/accounts/{accountId}/orders returns a lagging historical projection. A history row is not evidence that an order remains open. The open-orders response is bounded: inspect truncated and openOrderCount, and use its resync metadata only when truncated is false.

Use one account-scoped state model for positions, PnL, margin, orders and fills. Apply validated private events directly so every view uses the same account identity and freshness rules.

Validate completeness. A message may update only part of an account. Preserve the freshness state of fields the message does not establish; do not replace missing values with zero.

Separate command feedback. An HTTP response reports the order command’s outcome. Confirm working orders, fills and position changes through the corresponding account events.

Recover deliberately. After a gap, follow the channel’s replay or snapshot recovery instruction. If replay or payload coverage is insufficient, keep that scope stale until it can be reconciled. Reconnecting alone does not prove that missed changes have been recovered.

All account channels require ticket authentication. The channel contract assigns each channel an availability label. Read the current catalogue when connecting rather than treating every declared channel as an active source.

An order response reports command feedback. Order updates track lifecycle changes, fills record execution, and durability updates report saved-through progress. Correlate them using the order and sequence fields in each payload. Durability confirms persistence, while Canton settlement has its own confirmation.

A cancel affects only the unfilled remainder, and fills can arrive while cancellation is pending. Reconcile fills and positions before calculating a replacement quantity or treating exposure as zero. Keep an unknown outcome visible until the order read and streams resolve it.

Mark affected account state stale when authentication or continuity is lost. Restore the correct ticket and accepted channel scopes, then follow the channel’s supported recovery procedure. Complete position frames can update size, entry, mark, PnL and closure directly; a partial payload must not be treated as a complete account snapshot.

Seed and live sequence values are not universally interchangeable. Use only the replay and recovery rules defined for the channel. Routine live updates should not trigger account GETs, and a healthy socket alone must not make last-known balances appear fresh.

Confirm that the received fields cover the view or decision you are updating. Orders placed by another client, financial changes without an open position and owner funding activity may require information beyond a position update. If the available data cannot establish current state, keep the affected view stale or snapshot-only. See WebSocket recovery.

Order history, fill history and position history return one page with nextCursor and projection freshness. Their default page size is 50 and maximum is 100. Pass back the returned cursor and preserve your filters; stop when nextCursor is null. All support marketId; order and position history also support their documented status filters.

fundingPaidAtoms in a position episode is cumulative funding for that episode. It is not a separate funding-payment ledger. The public API and edel_funding tool do not provide per-payment funding rows. Do not synthesize those rows from successive snapshots or count cumulative funding repeatedly.