What is the Purpose of Webhook?

Real-Time Transaction Updates with Liminal Webhooks: Streamlining Blockchain Confirmations


A webhook serves a crucial role in the transaction process on Liminal. It is activated each time a transaction is completed, providing clients with real-time updates about the transaction status. This confirmation process is set in motion after a specific number of block confirmations occur on the blockchain, primarily for incoming or outgoing transactions. This ensures that clients are promptly informed about the completion of their transactions.

Events notified by Webhook

Webhook in Liminal are specifically designed to provide real-time updates about two primary types of events: send transactions and receive transactions.

Event NameDescription
Send TransactionsWhen a transaction is confirmed on the blockchain after being initiated from the Liminal platform, a 'send' event is triggered. This event signifies that a certain amount of cryptocurrency has been successfully transferred from one account to another. The associated webhook notifies the registered endpoint upon the confirmation of the transaction, providing all the necessary details such as transaction ID, the amount sent, the sender's and receiver's wallet details, and more. See full response
Receive TransactionsWhen a transaction is completed and the funds are received in the designated account, a 'receive' event is triggered. This event confirms the successful completion of the transaction. The webhook notification for this event provides the registered endpoint with the confirmation of the transaction completion, along with the relevant transaction details. Please note that this event only gets triggered after sufficient confirmations are received on blockchain as shown in this table. See full response.

By keeping track of these two crucial events, Liminal ensures that clients are always updated about their transaction status, enhancing transparency and efficiency in their operations.

Note: These events occur multiple times and notify your systems. Despite multiple occurrences, the data in the event remains the same. You can validate the payload received in the webhook request using the getTransfer API using the transaction hash to avoid duplicate entries in your system.