privy credentials delete
Revoke one app API credential by ID and clear its local stored value.
privy credentials delete [options] <credential-id>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
credential-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. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--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 credentials delete <credential-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 environment and current same-app key metadata; explicit access mode for creation.
- Production apps: Requires
--allow-productionand--yes. - Verification: One-time secret handled according to the explicit storage choice before fresh metadata comparison; deletion verified by absence.
- Retries: None.
- Caution: Deletion breaks consumers. Creation never automatically deletes old keys. Store failures after creation require inspecting the reported reference, not recreating blindly.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema credentials 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.