Skip to main content
Carrier: POST /v1/exchange (encrypted binary). Permission: Owner or live READ agent. Return a compact private account snapshot. The same command is available over WebSocket.
Fields below describe the SDK request before encryption and the decoded reply. The HTTP body is encrypted binary application/octet-stream, not JSON. Use a verified SDK client; the interactive playground is disabled.

​
Request fields

The client supplies the configured domain, account, policy, signer and verified session binding, and signs the canonical envelope.
​
Uint8Array (32 bytes)
required
Nonzero private request ID. Retain it for an exact retry; use a distinct ID for a different intent.
​
bigint (u64)
required
Current account authority epoch.
​
bigint (u64)
required
Authentication expiry in milliseconds, within the verified session and deployment limits.
​
"view"
required
Command discriminator.

​
Response fields

The example uses illustrative quote atoms and configured IDs, not live venue data. A view is not withdrawable cash or a proof of backing.
​
"view"
required
Compact account view discriminator.
​
bigint (u64)
required
Current account authority epoch.
​
bigint (i128)
required
Signed settled cash, in quote atoms.
​
bigint (i128)
required
Signed recognized unsettled funding, in quote atoms.
​
bigint (i128)
required
Explicit reservations, in quote atoms. Not the entire risk requirement.
​
Position[]
required
Configured market ID, precision version, signed lots and remaining signed basis. See positions.
​
Uint8Array[]
required
Retained private operation IDs. Query operation for receipts.

​
Behavior

View: epoch, signed cash/funding quote atoms, explicit held amount, signed position lots/remaining basis and retained operation IDs. Not withdrawable cash or proof of backing. Use account reads for optional qualified risk and valuation.

​
Errors and reconciliation

Typed errors are returned inside the encrypted reply, not as field-specific HTTP status codes. Invalid fields, expired or out-of-scope authority, conflicting intent IDs and unavailable required evidence fail closed. For qualified risk and valuation, use account reads. A delivery error or timeout is not a rejection. Reconnect with fresh attestation and reconcile the original operation ID before any economic retry. See lifecycle, limits and availability.