Skip to main content
WSS
Send wallet.create_twap with a connection-local id over wss://relay.testnet.kuru.io/relay/ws?account_id=<accountId> (or the mainnet host) and a wallet-bound JWT in the upgrade Authorization header. The request uses the same exact payload and signature rules as the REST method; omit the REST wallet and requestId fields. Use the signed trading account ID as the required upgrade account_id.
Automated TWAP execution is not implemented and remains work in progress. This method only stores an instruction where enabled; no service schedules or submits slices.
This is a slow operational request. Its bounded RPC simulation can hold later submissions on the same ordered WebSocket; use REST or a separate connection for latency-sensitive trading. BROADCAST only indicates asynchronous scheduling. Relay automatically sends transaction.outcome on this connection with the original id; no explicit subscription or client acknowledgement is required. Verify the intended on-chain state or events after a terminal outcome.
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
wallet.create_twap