Messages
{
"id": "sub-1",
"method": "transaction.subscribe",
"payload": {
"requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
"txHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
}{
"id": "sub-1",
"status": "SUBSCRIBED",
"requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
"txHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"retryable": false
}WebSocket methods
Subscribe to transaction
Recover a pending or retained Relay transaction outcome after reconnecting.
WSS
/
relay
/
ws
Send
transaction.subscribe with the server-assigned requestId and txHash from an earlier BROADCAST response. The authenticated WebSocket must be bound to the same trading wallet. This method does not rebroadcast the transaction.
New WebSocket submissions automatically receive outcomes on their submitting connection; explicit subscription is primarily for reconnect recovery. For a pending transaction, Relay responds SUBSCRIBED and later sends transaction.outcome. If its terminal outcome is still retained, Relay sends that outcome immediately instead.
Relay retains the latest 4,096 terminal outcomes per signer, shared across users. The limit is by count, not age, and replay may be unavailable after a signer restart. If the submission response was lost before either requestId or txHash arrived, a connection-local WS id cannot be used as a cross-connection lookup key. See Relay errors and outcomes for the CLOID and chain-state recovery path.Messages
{
"id": "sub-1",
"method": "transaction.subscribe",
"payload": {
"requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
"txHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
}{
"id": "sub-1",
"status": "SUBSCRIBED",
"requestId": "018f5ef2-88a1-7b41-a826-4b679010f87f",
"txHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"retryable": false
}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:
123transaction.subscribe
type:object
SUBSCRIBED acknowledgement
type:object