privy clients telegram delete
Remove a Telegram client override; falls back to app settings or disables Telegram for that client.
privy clients telegram 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 telegram delete <client-id> --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 and current configuration; editability/feature/provider-specific guards.
- Production apps: Requires
--allow-productionand--yes. - Verification: Fresh public configuration; masked or omitted secret values and real external login are not verified.
- Retries: None.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema clients telegram 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.