Get Route Status
This method aims to provide the status of the transaction
Last updated
This method aims to provide the status of the transaction
Last updated
Squid combines Axelar's infrastructure as well as bespoke on-chain analytics to provide status of cross-chain transactions. You can access this status using the getStatus
method on our SDK.
You can also check completion of most cross chain transactions on Squid by copying the transaction hash into . Note, for some Cosmos transactions and others in the future this will not work.
transactionId
string
Yes
The transaction hash
requestId
string
No
The request ID (legacy parameter)
integratorId
string
No
Your integrator ID
fromChainId
string
Yes
The source chain ID
toChainId
string
Yes
The destination chain ID
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
The quoteId
can be found at the top level of the route response. Including this parameter in status requests will enable volume and specific token activity sharing with integrators in the near future:
The most important response param is squidTransactionStatus
. This param will tell you what to show the user. There are 6 possible states:
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.
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.
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.
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.
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.
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 caller
The fromAddress
from the route request is used as the order.fromAddress
for refunds
This ensures that even if the transaction was initiated through a smart contract, the refund goes to the actual user
Generally, the best thing to do is to share https://axelarscan.io/gmp/<txHash>
with a user.
With the caveat that if you are doing a transaction between two Cosmos chains, this link may not be correct. For now we simply recommend you always using this approach, we are upgrading our status capability and the status endpoint will always return the correct block explorer link to share.
The response includes detailed information about both source and destination chains, transaction URLs, timing data, and the current status.