privy organizations wallets add
Bind an unbound wallet to an organization; this association is one-way.
privy organizations wallets add [options] <organization-id> <wallet-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
organization-id |
— |
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. |
--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”privy organizations wallets add <organization-id> <wallet-id> --dry-runprivy organizations wallets add <organization-id> <wallet-id> --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand 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-productionand--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.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema organizations wallets add.
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.