privy clients delete
Delete a frontend client configuration; app users and wallets remain shared and are not deleted.
privy clients delete [options] <client-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
client-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. |
--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 clients delete <client-id> --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Check app environment and same-app client; cookie inheritance requires a configured app domain.
- Production apps: Requires
--allow-productionand--yes. - Verification: Fresh exact-ID list comparison.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema clients delete.
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.