Returns the status of cross-chain bridging transaction using Socket
How this API is used in Socket :
The bridge status API is used to track whether a cross-chain bridging transaction has completed or not
In case of bridges such as Polygon Native Bridge where a claiming/exit transaction is required on the destination chain to claim tokens, the bridge status API can be used to alert a user when claiming is available
API-KEY needs to be passed in the headers while making the GET request
Returns the status of cross-chain transaction
NOTE : For Polygon Native Bridge and Arbitrum Native Bridge, the bridgeName paramater is required to be filled in. For the others, it is optional.
Description of response parameters :
Indicates successful response from endpoint, as intended.
Hash of source transaction
Status of transaction on source chain. Values in Types page.
Hash of destination transaction
Status of transaction on destination chain. Values in Types page.
ID of sending/source chain
ID of destination chain
Object metadata of sending token
Object metadata of receiving token
Price of fromAsset token in USD
Price of toAsset token in USD
Amount of token sent on sending chain
Amount of token received on the destination chain
User address on source chain
Recipient user address on destination chain
Boolean value indicating if this transaction was performed through Socket
Returns refuel tx status for Swap+Bridge+Refuel tx. It is returned null for non-refuel transactions.
Status of Refuel in Swap+Bridge+Refuel tx.
Hash of Refuel tx on destination chain
Status of Refuel tx on destination chain
NOTE ON REFUEL STATUS :
For a Swap+Refuel tx (where Refuel is the Bridge), the outer destinationTxStatus and destinationTransactionHash reflect the status of the destination tx.
For a Swap+Bridge+Refuel tx, the refuel object in /bridge-status response contains the status of refuel. The main Swap+Bridge bridging transaction status and hash can be checked from destinationTxStatus and destinationTransactionHash.