Delete wallet

Deletes the wallet from its exact owning custody target when that Provider supports wallet deletion.

DELETE/v1/walletsRun in dashboard

Provider, when supplied, is a consistency assertion.

Requires an API key with the wallets.execute action.

Headers

  • x-project-id · string · min length 1 · example prj_example

    Required for dashboard sessions. API keys use their assigned project.

  • Idempotency-Key · string

    Use a unique 1–255 printable ASCII key per operation. Reuse it with the same request on retries. An in-flight attempt returns 409; a changed request returns 422. Retry and recovery rules.

Request body

application/json · required

Delete wallet request body.

  • provider · string · one of local, fireblocks, privy, coinbase_cdp, para, turnkey, dfns, ibm_haven, anchorage, utila · example anchorage

    Optional consistency assertion for the Provider of the wallet being deleted.

  • walletId · string · required · min length 1 · example anchorage_wallet_123

    Provider wallet ID to delete from its exact owning target.

Responses

  • 200 Wallet deleted

    • data · object · required

      Delete wallet response payload.

      • walletId · string · required · min length 1 · example anchorage_wallet_123

        Wallet ID that was deleted.

      • deleted · boolean · required · always true · example true

        Deletion confirmation flag.

    • meta · object · required

      Response metadata.

      • requestId · string · required · min length 1 · example req_example

        Request identifier for tracing.

      • timestamp · string · required · format date-time · example 2025-01-01T00:00:00.000Z

        ISO 8601 timestamp.

  • 400 Bad Request

    • error · object · required

      Standard error payload.

      • code · string · required

        Machine-readable error code.

      • message · string · required

        Human-readable error message.

      • details · object

        Optional error details for debugging.

        • * · any

    • meta · object

      • requestId · string · min length 1 · example req_example

        Request identifier for tracing.

  • 401 Unauthorized

    Same fields as 400.

  • 403 Forbidden. Requires the wallets.execute action: an API key must hold it (a module's manage or execute also covers its read), and a signed-in member's organization role must include it. Without it the error is INSUFFICIENT_PERMISSIONS and error.details.action names the action. Any other 403 names its own reason.

    Same fields as 400.

  • 404 Not Found

    Same fields as 400.

  • 409 Conflict

    Same fields as 400.

  • 422 Unprocessable Entity

    Same fields as 400.

  • 500 Internal Server Error

    Same fields as 400.

Example request

curl -X DELETE 'https://api.solana.com/v1/wallets' \
  -H "Authorization: Bearer $SDP_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "anchorage",
    "walletId": "anchorage_wallet_123"
  }'

Example responses

{
  "data": {
    "walletId": "anchorage_wallet_123",
    "deleted": true
  },
  "meta": {
    "requestId": "req_example",
    "timestamp": "2025-01-01T00:00:00.000Z"
  }
}

Error responses use the standard error shape.

Is this page helpful?