Skip to main content
POST
Submits wallet.execute_batch. Use this method for normal order entry and cancellation integrations.
The example uses the verified mainnet WETHUSDC market, but its wallet, nonce, deadline, account ID, and signature are placeholders. Build and sign a fresh intent for the selected network before submitting.
string
required
New lowercase UUIDv7 for correlation.
string
default:"wallet.execute_batch"
required
Must be wallet.execute_batch.
string
required
Secondary trading EOA matching the bearer JWT.
object
required
Signed BatchIntent containing header, orders, cancelSlotIdxs, expectedOrderIds, and signature.
object | null
Normally null after onboarding.
The header requires accountId, market, authNonce, increasing nonce, Unix-second deadline, 32-byte clientOrderId, builder, and builderFeePps. Every integer is a canonical unsigned decimal string. Sign BatchIntent with the KuruTradingWallet EIP-712 domain: version 2, chain ID 143 on mainnet or 10143 on testnet, and the delegated trading EOA as verifyingContract (not the shared implementation or Relay address). Version-1 wallet signatures are invalid for the current implementation; rebuild and re-sign any pending intents created with that domain. AccountCore signer grants use their separate KuruAccountCore version-1 domain. See Trading-wallet Signing. Each native order requires side (BUY/SELL), quantity, price, tif (GTC/IOC/FOK), executionInstruction (NONE/POST_ONLY), and minSizeAfterBlock. Post-only requires GTC.
Up to 256 orders and 62 unique cancellations are accepted. expectedOrderIds must be parallel to cancelSlotIdxs; bind cancellations to current order IDs whenever possible.