Skip to main content
HTTP status: 409 · Title: “Wallet delegation not enabled”

​
When it fires

The API cannot act on the self-custodial wallet your API key is configured to trade from. Returned by POST /v1/trades and POST /v1/redemptions. Today this happens when the key is configured to trade from a smart account other than the key owner’s own. API v1 trades and redeems only from the key owner’s own account, so such a key is refused before anything is written. The detail says so. Wallet delegation (the permission that lets the Kash app connect your self-custodial wallet to the Kash protocol so that your transactions can be submitted to the protocol without a signing prompt each time) is granted in the Kash web app, at the Approve Kash step. If it is missing, trades accepted by the API fail at execution rather than returning this code synchronously; check the trade’s status on GET /v1/trades/{id}.

​
Why it happens

  • The key was issued to trade from an account other than your own.
  • The Approve Kash step was skipped during sign-in, or the web app has asked for a fresh approval that hasn’t been given yet.

​
How to fix

  • Use a key configured to trade from your user account. Issue one in the Kash web app (Settings → API Keys) or ask ZeroID support.
  • If delegation is missing, complete the Approve Kash step in the Kash web app. It is shown again when you next trade there.