Get Route Status
Squid extends the AxelarScan API and bespoke on-chain indexing in order to give details on the status of cross-chain transactions.
API Endpoint
Code Example
Request Parameters
transactionId
string
Yes
Transaction hash from the transaction submitted to the source chain
fromChainId
string
Yes
The source chain ID
toChainId
string
Yes
The destination chain ID
requestId
string
No
The request ID (legacy parameter)
quoteId
string
No
The quote ID from the route response. Passing this parameter will enable volume and token activity sharing with integrators in the near future
Getting Quote ID from Route Response
The quoteId
can be found at the top level of the route response:
Request Headers
x-integrator-id
Response Parameters
id
string
Transaction hash
status
string
Transaction status from Axelarscan (see status values below)
gasStatus
string
Transaction gas status returned from Axelarscan (see gas status values below)
isGMPTransaction
boolean
Returns true
if the transaction is a GMP transaction, false
if it is a bridge transfer
squidTransactionStatus
string
Simplified status for transaction (see squid transaction status values below)
axelarTransactionUrl
string
URL to view the transaction on Axelarscan
fromChain.transactionId
string
Transaction hash on the source chain
fromChain.blockNumber
number
Transaction block number on source chain
fromChain.callEventStatus
string
SquidMulticall contract event status relating to transactionId
on source chain
fromChain.callEventLog
array
SquidMulticall event logs for transactionId
on source chain
fromChain.chainData
object
Complete chain configuration and contract addresses for source chain
fromChain.transactionUrl
string
Block explorer URL for the source chain transaction
toChain.transactionId
string
Transaction hash on destination chain
toChain.blockNumber
number
Transaction block number on destination chain
toChain.callEventStatus
string
Latest SquidMulticall event status on destination chain
toChain.callEventLog
array
SquidMulticall event logs on destination chain
toChain.chainData
object
Complete chain configuration and contract addresses for destination chain
toChain.transactionUrl
string
Block explorer URL for the destination chain transaction
timeSpent
object
Timing breakdown showing time spent in different phases of the transaction
error
object
Error returned from Axelarscan GMP API
requestId
string
The request ID associated with the transaction
integratorId
string
The integrator ID associated with the transaction
Squid Transaction Status Values
Simplified status for transaction. There are 6 possible states:
SUCCESS
This indicates the transaction has completed on all chains. Whether a single chain, 2 chain or 3 chain call, the swap, stake, NFT purchase, bridge etc. has completed without any reversions and the user has received the intended funds.
NEEDS_GAS
This state is specific for Axelar transactions. If the gas price has spiked on the destination chain and execution cannot complete, Squid will return this status. The best user flow in this case is to send the user to Axelarscan to view the paused transaction.
ONGOING
There is nothing wrong, nothing to do, just relax and wait. The transaction should have an estimatedRouteDuration
in seconds that you can read from the /route
response. We generally recommend contacting support after either 15 minutes has passed, or double the estimatedRouteDuration
, whichever is larger.
PARTIAL_SUCCESS
This status indicates that the transaction has completed some of its steps. Currently, there is only one case that could cause this state. In the future there will be many, but we will provide more metadata around the PARTIAL_SUCCESS
. For now, this is what has happened:
The source chain transaction successfully executed, along with any swaps or contract calls.
The destination chain transaction has executed, but reverted during execution. This is usually due to slippage on volatile assets, but if you are trying to buy an NFT or do some cross-chain staking, then it could indicate that the custom hook had a failure.
If there is a partial success, the user will have received the bridged token in their wallet on the destination chain. In most cases this is axlUSDC.
NOT_FOUND
The Squid API cannot find an on-chain record of the transaction. This is usually due to our various services or service providers not having indexed the completed transaction. This state is often returned for 5-10 seconds after the transaction was executed, while chain indexing occurs.
This should not persist after maximum a few minutes (some chains such as Filecoin take a very long time to index, and for block inclusion). If it does, then get in touch with us on Discord.
REFUND_STATUS
This status is specific to failed Coral routes. When a Coral transaction fails, the funds are automatically refunded on the source chain. This is the default behavior for Coral routes when passing the user's address as the fromAddress
.
How Coral refunds work:
Funds are always transferred from the
msg.sender
on the source chain (this could be the user for direct calls to Coral, or a smart contract like Multicall)When refunded, funds are sent to the
order.fromAddress
which is encoded to the user, not the callerThe
fromAddress
from the route request is used as theorder.fromAddress
for refundsThis ensures that even if the transaction was initiated through a smart contract, the refund goes to the actual user
Example Response
Last updated