Skip to main content
POST
cURL

Overview

The GetIntentReceipt endpoint retrieves the receipt for a specific intent, providing detailed information about all transactions involved in the cross-chain execution.

Use Cases

  • Check the status of an executing intent
  • Retrieve transaction hashes for block explorer links
  • Monitor cross-chain transaction progress
  • Get detailed transaction information for analytics
  • Verify successful completion

Request Parameters

Required Fields

  • intentId (string): The unique identifier of the intent

Response

The response includes:
  • intentReceipt (IntentReceipt): Complete receipt with transaction details

IntentReceipt Structure

  • id (number): Internal database ID
  • intentId (string): Unique intent identifier
  • status (IntentStatus): Current status (QUOTED, COMMITTED, EXECUTING, SUCCEEDED, FAILED, ABORTED, INVALID, REFUNDED). See Intent Statuses
  • statusReason (string, optional): Why the intent reached its final status
  • ownerAddress (string): Wallet address that initiated the intent
  • originChainId (number): Source chain ID
  • destinationChainId (number): Destination chain ID
  • depositTransactionId (number): ID of deposit transaction
  • depositTransaction (IntentTransaction): Deposit transaction details
  • originTransactionId (number): ID of origin transaction
  • originTransaction (IntentTransaction): Origin chain transaction details
  • destinationTransactionId (number): ID of destination transaction
  • destinationTransaction (IntentTransaction): Destination chain transaction details
  • refundTransaction (IntentTransaction, optional): Refund transaction, when one was recorded. A pending or failed refund transaction doesn’t make the intent REFUNDED
  • updatedAt (string): Last update timestamp
  • createdAt (string): Creation timestamp

Failure Reasons

When an intent or one of its transactions doesn’t succeed, statusReason names the cause instead of just reporting a failure — for example a decoded revert, a likely out-of-gas execution, an origin precondition that wasn’t met (a short deposit), or a bridge that didn’t deliver, naming the bridge and its own explanation. The text is built for people, not for parsing — don’t match on it.

IntentTransaction Details

Each transaction object includes:
  • id (number): Transaction database ID
  • intentId (string): Associated intent ID
  • chainId (number): Chain where transaction occurred
  • fromAddress (string): Sender address
  • toAddress (string): Recipient address
  • tokenAddress (string): Token contract address
  • tokenAmount (number): Amount transferred
  • txnHash (string): Transaction hash for block explorer
  • status (TransactionStatus): Transaction status
    • UNKNOWN: Initial state
    • PENDING: Waiting to be mined
    • RELAYING: Being relayed
    • RELAYED: Relayed successfully
    • MINING: Being mined
    • SUCCEEDED: Confirmed on-chain
    • FAILED: Transaction failed
  • statusReason (string): Reason for failure (if failed)
  • calldata (string): Transaction calldata
  • metaTxnId (string): Meta-transaction ID (if gasless)
  • precondition (TransactionPrecondition): Pre-execution conditions
  • depositIntentEntry (DepositIntentEntry): Deposit signature details

Example

Polling Pattern

For real-time updates, poll this endpoint:
Use transaction hashes to create explorer links:
For streaming updates without polling, consider using WaitIntentReceipt instead.

Next Steps

  • Use transaction hashes to verify on block explorers
  • Check destination wallet balance to confirm receipt
  • Use GetIntent to retrieve the original intent details
  • Use SearchIntents to find related transactions

Body

application/json
intentId
string
required

Response

OK

intentReceipt
object
required