Recover a failed deposit with an owner signature
Return a failed or rejected deposit’s source-chain funds to a user-chosen recipient, authorized by the smart-account owner’s EIP-712 signature (not just the API key). The server reconstructs the RecoverDeposit typed data from the stored deposit and verifies it against the account via ERC-1271/ERC-6492, then runs the same claim + transfer path as the refund endpoint. EVM Nexus accounts created by the deposit modal only. Authenticate with an x-api-key (write scope).
Headers
API key for authentication (omit when sending Authorization)
"your-api-key"
Bearer platform token (e.g. forwarded by user-service). Takes precedence over x-api-key when both are present.
"Bearer eyJhbGciOi..."
Body
CAIP-2 chain identifier of the deposit (e.g. "eip155:8453")
^[a-z0-9]+:[a-zA-Z0-9]+$"eip155:8453"
Source transaction hash of the failed/rejected deposit
^0x[a-fA-F0-9]+$"0xabc123..."
Deposit smart account that received the funds
^0x[a-fA-F0-9]{40}$"0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91"
Source token address. Use the zero address for native transfers.
^0x[a-fA-F0-9]{40}$"0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91"
Address to receive the recovered tokens on the source chain
^0x[a-fA-F0-9]{40}$"0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91"
Unix timestamp (seconds) after which the signature is no longer valid
1800000000
Raw 65-byte ECDSA signature by the account owner over the RecoverDeposit typed data
^0x[a-fA-F0-9]{130}$"0x1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111"