privy config sessions update

Update app-user session/token lifetimes and verify each changed field.

Usage

privy config sessions update [options]

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.
--session-timeout-minutes <integer>	App-user session duration: 1–400 days in minutes. UI default: 43200 (30 days).
--session-inactivity-window-minutes <integer>	App-user inactivity/refresh duration: 1–400 days in minutes. UI default: 43200.
--access-token-lifetime-minutes <integer>	App-user access-token lifetime: 10–1440 minutes. UI default: 60.
--id-token-lifetime-minutes <integer>	App-user identity-token lifetime: 10–1440 minutes. UI default: 600.
--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

privy config sessions update --access-token-lifetime-minutes 30 --diff
privy config sessions update --session-timeout-minutes 43200 --dry-run

Behavior

• Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
• Scope: app
• Before it runs: Check selected app environment and current settings.
• Production apps: Requires --allow-production and --yes.
• Verification: Fresh read-back of each changed field; set comparison where declared.
• Retries: None.

Related guides

• Security settings
• Failure recovery

Inspect the full contract locally with privy schema config sessions update.