privy access denylist clear
Clear denylist entries in an explicit scope; can change app access.
privy access denylist clear [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. |
--type <string> |
Explicit scope: all entries, or accepted allowlist invitations only. Irreversible. |
--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 access denylist clear --type all --dry-runBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Selected app environment, full bounded current list, same-app IDs/duplicate checks.
- Production apps:
--allow-productionand--yes. - Verification: Fresh entries or absence; login enforcement is separate.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema access denylist clear.
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.