Skip to main content
For state-changing operations (creating wallets, signing requests), add an idempotency-key header to safely retry failed requests.

Usage

Requirements

How It Works

  1. Include a unique idempotency-key header with your request
  2. If the request fails due to network issues, retry with the same key
  3. MPCVault returns the cached response if the key was already used
  4. This prevents duplicate wallet creation or transaction signing

When to Use

  • createWallet - Prevent duplicate wallet creation
  • createSigningRequest - Prevent duplicate transaction requests
  • createBatchPayment - Prevent duplicate batch payments
Read-only operations like getWalletList don’t require idempotency keys.