LI.FI — Populate a step with transaction data
lifi_post_v1_advanced_steptransactionThis endpoint expects a full Step object which usually is retrieved by calling the /advanced/routes endpoint and selecting the most suitable Route. Afterwards the transaction for every required Step can be retrieved using this endpoint.
Uses the caller's OpenAny gateway credentials. Charges and authorization are determined by the gateway.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Object that represents one step of a `Route` | |
| denyPools | No | One to 100 AMM pool or Solana venue identifiers to exclude when building transaction data. If the route was requested with `options.pools.deny`, you must pass the same list again for each step: pool exclusions are request-scoped and are not carried in the returned Step. Without it, swaps are re-quoted with no exclusions, so the transaction can use an excluded pool or venue. Repeat the query parameter for multiple entries, as with `/v1/quote`. Each entry is a non-zero Uniswap V2/V3 EVM pool address (`0x` + 40 hex), a Uniswap V4 `-` identifier, where `poolId` is `0x` + 64 hex, or a Solana venue program ID (base58). EVM pool exclusion is supported only by `fly`; Solana venue exclusion only by `jupiter`, `titan` and `okx`. If the list holds a Solana program ID, a step that swaps on Solana through any other exchange is rejected with a 400 error instead of being built without the exclusion. Keep the Step object in the JSON request body. | |
| skipSimulation | No | Parameter to skip transaction simulation. The quote will be returned faster but the transaction gas limit won't be accurate. | |
| svmPriorityFeeLevel | No | Priority fee level for Solana Virtual Machine (SVM) transactions. | |
| mayanNonEvmPermitSignature | No | Mayan specific option to bridge from non-EVM chain to Hyperliquid | |
| svmMaxSupportedTransactionVersion | No | Maximum Solana transaction version the client can sign. Defaults to 0; omission or null uses v0. Set to 1 to allow V1 where enabled for the environment. Jito requests always use v0. Size overflow may fall back to v0. Read transactionRequest.svmTransactionVersion for the version actually built. Ignored for source chains other than Solana. |