> ## Documentation Index > Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt > Use this file to discover all available pages before exploring further. # Get details for a route step > Enriches a route step with full transaction details and updated estimates. Pass a step object from a previous routes response as the request body (not wrapped under any key). ## OpenAPI ````yaml /openapi/client-api.yaml post /clients/me/integrations/lifi/route-step-details openapi: 3.1.0 info: title: Portal Client API version: '3.0' description: > The Portal Client API provides endpoints for managing wallets, building transactions, and interacting with blockchain networks. All endpoints require authentication via a Client API Key or Client Session Token (CST) passed as a Bearer token. ## Base URL `https://api.portalhq.io/api/v3` ## Authentication Include your Client API Key or Client Session Token as a Bearer token in the `Authorization` header of every request. ## Chain ID Format Chain parameters use either friendly names (e.g. `ethereum`, `solana`) or CAIP-2 format (e.g. `eip155:1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`). When using CAIP-2 format in URLs, ensure the colon is URI-encoded (`%3A`). servers: - url: https://api.portalhq.io/api/v3 description: Production security: - bearerAuth: [] tags: - name: Clients description: Core client management endpoints - name: Wallet description: >- Read wallet state — balances, NFTs, transaction history, capabilities, and transaction details - name: Transactions description: Build, broadcast, and evaluate blockchain transactions - name: Funding description: Fund wallets with testnet tokens - name: Wallet Shares description: Manage signing and backup share pairs - name: Delegations description: Manage token approvals, revocations, and delegated transfers - name: Session Keys description: Manage EIP-7702 session keys for smart accounts - name: 0x description: Token swap endpoints powered by the 0x protocol - name: Yield.xyz description: Yield opportunities and staking actions powered by Yield.xyz - name: Li.Fi description: Cross-chain swaps and bridging powered by Li.Fi - name: Blockaid description: Transaction and address security scanning powered by Blockaid - name: Hypernative description: >- Transaction, address, token, and NFT security scanning powered by Hypernative - name: Noah description: KYC onboarding, payins, and payouts powered by Noah - name: Meld description: Buy and sell crypto with fiat through aggregated providers powered by Meld - name: EIP-7702 description: EIP-7702 account type detection and authorization management - name: Deprecated description: >- Legacy endpoints scheduled for removal. Use the newer equivalents listed in each endpoint's description. paths: /clients/me/integrations/lifi/route-step-details: post: tags: - Li.Fi summary: Get details for a route step description: > Enriches a route step with full transaction details and updated estimates. Pass a step object from a previous routes response as the request body (not wrapped under any key). operationId: getLifiRouteStepDetails requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/LifiStepRequest' responses: '200': description: Step details retrieved successfully content: application/json: schema: $ref: '#/components/schemas/LifiStepResponse' '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: LifiStepRequest: type: object description: | A step object as returned by `/lifi/routes` (or `/lifi/quote`). The body is the step itself, not wrapped under a `step` key. Chain ID fields use CAIP-2 format on input, matching what Portal returned to you. required: - id - type - tool - toolDetails - action additionalProperties: true properties: id: type: string description: Unique step identifier from the prior routes/quote response. type: type: string description: Step type (e.g. `swap`, `cross`, `lifi`). tool: type: string description: Identifier of the tool/protocol executing the step. toolDetails: type: object required: - key - name - logoURI properties: key: type: string name: type: string logoURI: type: string action: type: object required: - fromChainId - toChainId - fromAmount - fromToken - toToken properties: fromChainId: type: string description: Source chain ID in CAIP-2 format. toChainId: type: string description: Destination chain ID in CAIP-2 format. fromAmount: type: string fromToken: type: object required: - address - symbol - decimals - chainId - name properties: address: type: string symbol: type: string decimals: type: integer chainId: type: string description: Chain ID in CAIP-2 format. name: type: string coinKey: type: string priceUSD: type: string logoURI: type: string toToken: type: object required: - address - symbol - decimals - chainId - name properties: address: type: string symbol: type: string decimals: type: integer chainId: type: string description: Chain ID in CAIP-2 format. name: type: string coinKey: type: string priceUSD: type: string logoURI: type: string fromAddress: type: string toAddress: type: string slippage: type: number estimate: type: object additionalProperties: true integrator: type: string includedSteps: type: array items: type: object additionalProperties: true referrer: type: string execution: type: object additionalProperties: true transactionRequest: type: object additionalProperties: true LifiStepResponse: type: object properties: data: type: object properties: rawResponse: type: object description: >- Enriched step with `transactionRequest` and updated `estimate`. Chain ID fields are returned in CAIP-2 format. additionalProperties: true ErrorResponse: type: object properties: error: type: string description: Error message describing what went wrong securitySchemes: bearerAuth: type: http scheme: bearer description: > Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header. ````