Rescan a transaction

Initiates a rescan for a transaction by passing either transactionHash or sequenceId in the request body. This will refresh transaction records if there are updates.

Initiates a rescan for a transaction by passing either transactionHash or sequenceId in the request body. When triggered, this process checks the blockchain for the specified transaction and updates the missed transaction records if Liminal previously missed them during the syncing process.

When to use this API

The Rescan transaction API is useful when you have an existing incoming transaction on-chain but it does not reflect on Vaults. The transaction’s on-chain time versus when it is recorded in the transaction history may vary. In this case, calling the API will retrigger the transaction to sync any pending ones.

📘

Note

  1. The Transactions History is updated when a transaction is successfully rescanned. You will receive a webhook notification for the missing transaction.
  2. Limitation: The Rescan API processes an existing transaction after it has reached the minimum required on-chain block confirmations. Once confirmed, it retriggers the existing transaction to be synced.
Body Params
string

Hash of the transaction to be rescanned. Required if sequenceId is not provided.

string

Unique identifier for the transaction sequence. Required if transactionHash is not provided.

string
enum
required

Blockchain network identifier.

Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json; charset=utf-8