privy integrations kraken update
Configure kraken. Complete Kraken Embed configuration; requires explicit provider environment and credentials. No purchases or transfers.
privy integrations kraken 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. |
--enabled <boolean> |
Explicit integration enabled state; credentials are not silently reused from masked read-back. |
--is-staging <boolean> |
Explicit Kraken staging versus production provider environment. Separate from Privy app dev/prod. |
--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”privy integrations kraken update --body - --dry-runBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand any required confirmations. - Scope: app
- Verification: Allowlisted read-back; masked credentials are not exact-value proof; no external integration verification.
- Retries: No automatic write retries.
Related guides
Section titled “Related guides”Inspect the full contract locally with privy schema integrations kraken 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.