privy global-wallet availability update

Make this app available/unavailable as a cross-app wallet provider, after explicit eligibility and access-impact checks.

Usage

privy global-wallet availability update [options]

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.
--availability <string>	Public makes this app a cross-app wallet provider; private pauses other apps’ access. Does not publish the CLI to npm. invite_only/pending are readable server states, not writable inputs.
--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

privy global-wallet availability update --availability public --diff
privy global-wallet availability update --availability private --confirm-name <app-name> --allow-access-change --yes

Behavior

• Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
• Scope: app
• Before it runs: Owning-account approval and selected-app environment; verified enabled cookies, or custom experience for development. No implicit feature request or billing changes.
• Verification: Fresh availability and unchanged known controls. Pending review is not published; no automatic retries.

Related guides

• Integrations and clients
• Failure recovery

Inspect the full contract locally with privy schema global-wallet availability update.