privy webhooks signing-key save

Retrieve an endpoint signing key directly into OS credential storage; never print it.

Usage

privy webhooks signing-key save [options] <endpoint-id>

Arguments

Argument	Description
endpoint-id	—

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.
--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 webhooks signing-key save <endpoint-id> --yes

Behavior

• Changes data: yes. Preview with --dry-run, then run with --yes and any required confirmations.
• Scope: app
• Before it runs: Check app environment and endpoint state. Delete/test/resend/enable require exact --confirm-url. Subscriptions affect all app endpoints.
• Production apps: Requires --allow-production and --yes.
• Verification: List/status read-back for configuration; notification submissions are acknowledgements, not successful delivery.
• Retries: None.
• Caution: Callbacks can disclose user data or repeat receiver business actions. Only use authorized destinations.

Related guides

• Webhooks
• Failure recovery

Inspect the full contract locally with privy schema webhooks signing-key save.