privy webhooks subscriptions update
Replace subscriptions for ALL endpoints in this app.
privy webhooks subscriptions 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. |
--subscriptions <json> |
Complete event subscription array for ALL app endpoints; [] unsubscribes all. Privy validates event names. |
--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 webhooks subscriptions update --subscriptions '["user.created"]' --diffprivy webhooks subscriptions update --subscriptions "[]" --yesBehavior
Section titled “Behavior”- Changes data: yes. Preview with
--dry-run, then run with--yesand 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-productionand--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
Section titled “Related guides”Inspect the full contract locally with privy schema webhooks subscriptions 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.