privy domains delete
Remove a cookie domain with explicit confirmation of session impact.
privy domains delete [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. |
--allow-session-impact |
Acknowledge that disabling/deleting cookie domains can log out app users. |
--confirm-domain <hostname> |
Confirm the current cookie domain before removing it. |
--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 domains delete --confirm-domain example.com --allow-session-impact --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Before it runs: Check environment, current domain and optional same-app web client. No implicit domain replacement or allowed-origin expansion.
- Production apps: Requires
--allow-productionand--yes. - Verification: Fresh configuration/status read-back. DNS verification is reported separately; an owned DNS domain is required.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema domains 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.