User Flows and Examples
Transaction status tracking
Complete guide to checking cross-chain transaction statuses using the LI.FI API
Transaction Status
This guide explains how to check the status of cross-chain and swap transactions using the /status
endpoint provided by LI.FI.
Querying the Status Endpoint
To fetch the status of a transfer, the /status
endpoint can be queried with:
- sending transaction hash
- receiving transaction hash
- transactionId
Only one of the above values are required and need to be passed in txHash
param.
Required:
txHash
Optional:
fromChain
: Speeds up the request (recommended)toChain
bridge
For swap transactions, set fromChain
and toChain
to the same value. The bridge
parameter can be omitted.
Sample Response
Status Values
Status | Description |
---|---|
NOT_FOUND | Transaction doesn’t exist or not yet mined. |
INVALID | Hash is not tied to the requested tool. |
PENDING | Bridging is still in progress. |
DONE | Transaction completed successfully. |
FAILED | Bridging process failed. |
Substatus Definitions
PENDING
WAIT_SOURCE_CONFIRMATIONS
: Waiting for source chain confirmationsWAIT_DESTINATION_TRANSACTION
: Waiting for destination transactionBRIDGE_NOT_AVAILABLE
: Bridge API is unavailableCHAIN_NOT_AVAILABLE
: Source/destination chain RPC unavailableREFUND_IN_PROGRESS
: Refund in progress (if supported)UNKNOWN_ERROR
: Status is indeterminate
DONE
COMPLETED
: Transfer was successfulPARTIAL
: Only partial transfer completed (common for across, hop, stargate, amarok)REFUNDED
: Tokens were refunded
FAILED
NOT_PROCESSABLE_REFUND_NEEDED
: Cannot complete, refund neededOUT_OF_GAS
: Transaction ran out of gasSLIPPAGE_EXCEEDED
: Received amount too lowINSUFFICIENT_ALLOWANCE
: Not enough allowanceINSUFFICIENT_BALANCE
: Not enough balanceEXPIRED
: Transaction expiredUNKNOWN_ERROR
: Unknown or invalid stateREFUNDED
: Tokens were refunded