Skip to main content
POST
cURL

Overview

The RetryIntent endpoint repairs a failed user-submitted deposit flow by validating a replacement deposit transaction hash, marking the deposit leg as confirmed, and requeueing downstream execution.

Use Cases

  • Recover from a failed or dropped deposit transaction
  • Resubmit a deposit with a corrected transaction hash
  • Resume execution of an intent that failed during the deposit phase

Request Parameters

Required Fields

  • intentId (string): The unique ID of the intent to retry
  • depositTransactionHash (string): The transaction hash of the new or corrected deposit transaction

Response

  • intentId (string): The ID of the retried intent
  • intentStatus (IntentStatus): Updated status of the intent after retry

Examples

Retry a Failed Deposit

With the Trails SDK

The replacement deposit transaction must be confirmed on-chain before calling this endpoint. The depositTransactionHash must correspond to a valid on-chain transaction that deposits the correct token and amount to the intent address.

Next Steps

GetIntentReceipt

Check the receipt after retrying

WaitIntentReceipt

Stream updates until the intent completes

Body

application/json
intentId
string
required
depositTransactionHash
string
required

Response

OK

intentId
string
required
intentStatus
enum<string>
required

Represented as uint8 on the server side

Available options:
QUOTED,
COMMITTED,
EXECUTING,
FAILED,
SUCCEEDED,
ABORTED,
REFUNDED,
INVALID