Skip to main content
POST
Recover a failed deposit with an owner signature

Headers

x-api-key
string

API key for authentication (omit when sending Authorization)

Example:

"your-api-key"

authorization
string

Bearer platform token (e.g. forwarded by user-service). Takes precedence over x-api-key when both are present.

Example:

"Bearer eyJhbGciOi..."

Body

application/json
depositId
string
required

Deposit id, as returned by GET /deposits. Identifies the row directly: one transaction can produce several deposits, so a {chain, txHash, account, token} tuple does not.

Pattern: ^\d+$
Example:

"2551"

destination
string
required

Address to receive the recovered tokens on the deposit's source chain. Covered by the signature, so the caller cannot redirect an authorized recovery.

Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91"

signature
string
required

Signature by the deposit recipient over the RecoverDeposit typed data, in whatever form that account verifies: raw ECDSA (EOA), ERC-1271 (deployed smart account), or ERC-6492-wrapped (undeployed).

Required string length: 132 - 8194
Pattern: ^0x([a-fA-F0-9]{2})+$
Example:

"0x1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111"

Response

Deposit recovered; funds returned on the source chain

message
string
required
transactionHash
string
required
amount
string
required