COcosmos
Transaction

GET /v2/tx/status

Get the status of the specified transaction and any subsequent IBC or Axelar transfers if routing assets cross chain. The transaction must have previously been submitted to either the /submit or /track endpoints.

Request

Query parameters

tx_hashstring required

Hex encoded hash of the transaction to query for

chain_idstring required

Chain ID of the transaction

Response

The status of the transaction and any subsequent ibc or Axelar transfers.

state'STATE_SUBMITTED' | 'STATE_PENDING' | 'STATE_ABANDONED' | 'STATE_COMPLETED_SUCCESS' | 'STATE_COMPLETED_ERROR' | 'STATE_PENDING_ERROR' required

Transaction state:

  • STATE_SUBMITTED - The initial transaction has been submitted to Skip Go API but not observed on chain yet
  • STATE_PENDING - The initial transaction has been observed on chain, and there are still pending actions
  • STATE_COMPLETED_SUCCESS - The route has completed successfully and the user has their tokens on the destination. (indicated by transfer_asset_release)
  • STATE_COMPLETED_ERROR - The route errored somewhere and the user has their tokens unlocked in one of their wallets. Their tokens are either on the source chain, an intermediate chain, or the destination chain but as the wrong asset. (Again, transfer_asset_release indicates where the tokens are)
  • STATE_ABANDONED - Tracking for the transaction has been abandoned. This happens if the cross-chain sequence of actions stalls for more than 10 minutes or if the initial transaction does not get observed in a block for 5 minutes.
  • STATE_PENDING_ERROR - The overall transaction will fail, pending error propagation
statusstring

A high-level status indicator for the transaction's completion state.

Changes

No recorded changes to this operation across all 1 revision of this API.