privy accounts features custom-jwt update
Explicitly enable/disable the account JWT capability in a free, all-development workspace; does not configure app authentication.
privy accounts features custom-jwt 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. |
--confirm-account <name> |
Exact workspace name; affects every app in this account. |
--allow-access-change |
Acknowledge account-wide third-party authentication capability change. |
--body <json> |
JSON body, or - to read stdin. |
--file <path> |
JSON body file, or - to read stdin. |
--feature-name <string> |
Fixed supported feature; not a generic paid-feature activation endpoint. |
--enabled <boolean> |
Account-wide capability. Disable is refused while any app has JWT auth enabled. |
--diff |
Read live state and show changes WITHOUT writing (requires login). |
Global options such as --app, --account and --profile also apply. See the command reference overview.
Examples
Section titled “Examples”privy accounts features custom-jwt update --enabled true --dry-run --account <account-id>Behavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: account
- Before it runs: At most100 apps; disable refuses any active app JWT authentication. Recheck account membership, app auth, capabilities and billing before writing.
- Verification: Account flag read-back, unchanged app authentication/other known feature flags and billing tier; no automatic retry or rollback.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema accounts features custom-jwt 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.