LI.FI — Populate a step with transaction data

Retrieve populate a step with transaction data with the LI.FI API. Supply an action and a transaction ID. Sample fields include addresses and symbols. Use it for on-chain or crypto market research. The POST request schema also lists denyPools, skipSimulation, mayanNonEvmPermitSignature. Use the response in a DeFi workflow for the selected protocol, and compare the request and response with the provider example.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body*object

body

Object that represents one step of a `Route`
Optional parameters (5)
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.
Parameter to skip transaction simulation. The quote will be returned faster but the transaction gas limit won't be accurate.
Mayan specific option to bridge from non-EVM chain to Hyperliquid
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.
Priority fee level for Solana Virtual Machine (SVM) transactions.

Sample response

{
  "action": {
    "fromAddress": "0x552008c0f6870c2f77e5cC1d2eb9bdff03e30Ea0",
    "fromAmount": "100000000",
    "fromChainId": 1,
    "fromToken": {
      "address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
      "chainId": 1,
      "coinKey": "USDC",
      "decimals": 6,
      "logoURI": "https://raw.githubusercontent.com/trustwallet/assets/master/blockchains/ethereum/assets/0xA0b86991c6",
      "name": "USD Coin",
      "priceUSD": "1.0002350525",
      "symbol": "USDC",
      "tags": [],
      "verificationStatus": "verified",
      "verificationStatusBreakdown": []
    },
    "slippage": 0.005,
    "toAddress": "0x552008c0f6870c2f77e5cC1d2eb9bdff03e30Ea0",
    "toChainId": 10,
    "toToken": {
      "address": "0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85",
      "chainId": 10,
      "coinKey": "USDC",
      "decimals": 6,
      "logoURI": "https://raw.githubusercontent.com/trustwallet/assets/master/blockchains/ethereum/assets/0xA0b86991c6",
      "name": "USD Coin",
      "priceUSD": "1.0008373187",
      "symbol": "USDC",
      "tags": [],
      "verificationStatus": "verified",
      "verificationStatusBreakdown": []
    }
  },
  "estimate": {
    "approvalAddress": "0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE",
    "executionDuration": 2,
    "feeCosts": [
      {}
    ],
    "fromAmount": "100000000",
    "fromAmountUSD": "100.0235",
    "gasCosts": [
      {}
    ],
    "toAmount": "99739730",
    "toAmountMin": "99739730",
    "toAmountUSD": "99.8232",
    "tool": "across"
  },
  "id": "f7623b70-2446-47a7-a306-2f67fa59301f:0",
  "includedSteps": [
    {
      "action": {},
      "estimate": {},
      "id": "fad92fca-4184-40f8-a88c-7e840f1aceea",
      "tool": "feeCollection",
      "toolDetails": {},
      "type": "protocol"
    }
  ],
  "integrator": "lifi-api",
  "stepSimulation": {
    "gasSource": "simulation",
    "status": "success"
  },
  "tool": "across",
  "toolDetails": {
    "key": "across",
    "logoURI": "https://raw.githubusercontent.com/lifinance/types/main/src/assets/icons/bridges/across.svg",
    "name": "AcrossV4"
  },
  "transactionId": "0x5adb1acd899c00f65673bcc10757f4a18281d5d8ad98f8ef29282392d4969639",
  "transactionRequest": {
    "chainId": 1,
    "data": "0x1794958f000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000",
    "from": "0x552008c0f6870c2f77e5cC1d2eb9bdff03e30Ea0",
    "gasLimit": "0x425c4",
    "gasPrice": "0x2d4a467",
    "to": "0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE",
    "value": "0x0"
  },
  "type": "lifi"
}

Response result

Response structure

Inferred from examples
  • actionobject
    • fromAddressstring
    • fromAmountstring
    • fromChainIdinteger
    • fromTokenobject
      • addressstring
      • chainIdinteger
      • coinKeystring
      • decimalsinteger
      • logoURIstring
      • namestring
      • priceUSDstring
      • symbolstring
      • tagsunknown[]
      • verificationStatusstring
      • verificationStatusBreakdownunknown[]
    • slippagenumber
    • toAddressstring
    • toChainIdinteger
    • toTokenobject
      • addressstring
      • chainIdinteger
      • coinKeystring
      • decimalsinteger
      • logoURIstring
      • namestring
      • priceUSDstring
      • symbolstring
      • tagsunknown[]
      • verificationStatusstring
      • verificationStatusBreakdownunknown[]
  • estimateobject
    • approvalAddressstring
    • executionDurationinteger
    • feeCostsobject[]
    • fromAmountstring
    • fromAmountUSDstring
    • gasCostsobject[]
    • toAmountstring
    • toAmountMinstring
    • toAmountUSDstring
    • toolstring
  • idstring
  • includedStepsobject[]
    • actionobject
    • estimateobject
    • idstring
    • toolstring
    • toolDetailsobject
    • typestring
  • integratorstring
  • stepSimulationobject
    • gasSourcestring
    • statusstring
  • toolstring
  • toolDetailsobject
    • keystring
    • logoURIstring
    • namestring
  • transactionIdstring
  • transactionRequestobject
    • chainIdinteger
    • datastring
    • fromstring
    • gasLimitstring
    • gasPricestring
    • tostring
    • valuestring
  • typestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use LI.FI — Populate a step with transaction data with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.