simulationId for subsequent validation.
tokenIn, tokenOut, and amountIn), use the batch endpoint:
transactions (an array of TransactionDto) instead of transaction. The response contains a results array in the same order — each item has the same shape as a single /simulate response, with its own simulationId for /validate. Up to 5 transactions per request.
Request Parameters
Top-level fields
Transaction fields
Response
Examples
- Token Swap
- Vault Deposit
- DelegateCall
Simulate a swap from ETH to USDC on Ethereum mainnet.
Handling Simulation Errors
Whenresult.status is "Error", the result.error field contains details about why the transaction would fail. Common causes:
- Contract revert — The transaction would revert on-chain (e.g., insufficient balance, failed require check)
- Invalid calldata — The
datafield doesn’t match any function signature on the target contract - Out of gas — The transaction requires more gas than available
Updated
