Skip to content
CLIUnofficial

privy wallets update

Update wallet name or unowned-wallet controls; arrays replace existing settings.

Usage

Section titled “Usage”
Terminal window
privy wallets update [options] <wallet-id>

Arguments

Section titled “Arguments”
Argument Description
wallet-id —

Options

Section titled “Options”
Option Description
--dry-run Validate and print the API request without network access or credentials.
--yes Confirm this mutation or export.
--confirm-owner <id> Explicitly confirm assigning this owner; later control changes require owner authorization.
--body <json> JSON body, or - to read stdin.
--file <path> JSON body file, or - to read stdin.
--display-name <string> Wallet display name; JSON null clears it.
--owner-id <string> Owner user DID or key-quorum ID. Assigning an owner requires --confirm-owner with the same ID and makes future control changes require owner authorization.
--policy-ids <json> Complete attached-policy array (zero or one policy); [] detaches the current policy.
--additional-signers <json> Complete signer array: {signer_id, override_policy_ids:[]}. Replaces all existing additional signers.
--entity <object> Organization binding {type:“organization”,id:“…”}. Can be assigned once; cannot subsequently be changed.
--diff Read live state and show changes WITHOUT writing (requires login).
--allow-production Explicitly allow this production mutation; also requires --yes.

Global options such as --app, --account and --profile also apply. See the command reference overview.

Examples

Section titled “Examples”
Terminal window
privy wallets update <wallet-id> --display-name Treasury --diff
privy wallets update <wallet-id> --policy-ids '["policy-id"]' --yes

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Read app environment, wallet and referenced resources. Control changes on owned wallets require approval. New owner assignment requires --confirm-owner.
  • Production apps: Requires --allow-production and --yes.
  • Verification: Fresh exact-ID wallet lookup and comparison; exports are job submissions.
  • Retries: None.
  • Caution: Changing owners/policies/signers changes control of funds, but does not execute a transaction.
Section titled “Related guides”

Inspect the full contract locally with privy schema wallets update.

Privy CLI is an unofficial, community project by Samarth Saxena. Not affiliated with or endorsed by Privy. The Privy name and wordmark belong to Privy. It uses undocumented dashboard APIs that can change.