Skip to main content
WSS
Relay sends transaction.outcome automatically for successful WebSocket submissions on the submitting connection. It includes the original client id, Relay requestId, and txHash; no explicit subscription or client acknowledgement is required. An immediate submission rejection has no outcome subscription. After a reconnect subscription, the outcome instead carries the new subscription id. A retained terminal outcome may arrive immediately in response to transaction.subscribe, without a SUBSCRIBED acknowledgement. Terminal statuses are CONFIRMED, REVERTED, REPLACED, and UNKNOWN. CONFIRMED reflects finality and successful outer-transaction execution, but the currently deployed implementation does not prove the intended trading-wallet action ran. Reconcile the expected trading events and resulting account/order state before treating the logical action as complete. See Relay errors and outcomes for status details and recovery limits.
bearerAuth
type:http

Wallet-bound JWT supplied in the WebSocket upgrade Authorization header.

method
type:string

GET

query
type:object
account_id
type:string
required

Exactly one canonical positive uint40 Kuru trading account ID (1 through 1099511627775), without leading zero, sign, or whitespace.

Example: 123
transaction.outcome
type:object