privy config ip-allowlist update
Replace app-secret server-API IP restrictions; may block existing backend consumers.
privy config ip-allowlist update [options]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. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--allowed-ips <json> |
Complete IPv4/IPv6/CIDR array, maximum 500 matching the dashboard. [] removes the restriction. Does not alter local firewall/network settings. |
--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 ip-allowlist update --allowed-ips '["203.0.113.0/24"]' --dry-runprivy config ip-allowlist update --allowed-ips "[]" --diffBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Check selected app environment and current settings.
- Production apps: Requires
--allow-productionand--yes. - Verification: Fresh read-back of each changed field; set comparison where declared.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema config ip-allowlist 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.