Skip to content
CLIUnofficial

privy providers telegram update

Configure an app Telegram bot or client override; does not silently enable app login.

Usage

Section titled “Usage”
Terminal window
privy providers telegram update [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.
--bot-id <string> Bot token numeric prefix; supply with bot_secret through stdin.
--bot-name <string> Telegram bot username.
--seamless-auth-enabled <boolean> Enable seamless Telegram authentication for this configuration.
--diff Read live state and show changes WITHOUT writing (requires login).
--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”
Terminal window
privy providers telegram update --body - --yes < /dev/stdin

Behavior

Section titled “Behavior”
  • Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
  • Scope: app
  • Before it runs: Selected app/environment and current configuration; editability/feature/provider-specific guards.
  • Production apps: Requires --allow-production and --yes.
  • Verification: Fresh public configuration; masked or omitted secret values and real external login are not verified.
  • Retries: None.
Section titled “Related guides”

Inspect the full contract locally with privy schema providers telegram update.

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.