privy config client-key-export update
Configure client-key-export. Allow client-side wallet-key export. Account feature and nonlegacy wallet mode required; no actual export.
privy config client-key-export update [options]Options
Section titled “Options”| Option | Description |
|---|---|
--dry-run |
Validate and print the API request without network access or credentials. |
--allow-access-change |
Acknowledge cross-app access or customer authentication impact. |
--confirm-name <name> |
Exact selected app name, verified against fresh state. |
--yes |
Confirm this mutation or export. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--enabled <boolean> |
Allow client-side wallet-key export. Account feature and nonlegacy wallet mode required; no actual 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 config client-key-export update --body '{"enabled":true}' --dry-runBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema config client-key-export 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.