Skip to main content
PATCH
Update Notification Preferences
Change which account notifications Sequenzy emails you about this workspace. This endpoint requires the companies:manage scope. Reading the current values only requires account:read. Events you do not include keep their current value. The response returns the full set either way, so you never have to merge state yourself. This endpoint always acts on the API key’s own user and can never change a teammate’s settings. Instant form-submission notifications stop after 50 per workspace per UTC day. Form submissions continue to be processed after that cap; only the account-notification email is suppressed.
Requests whose User-Agent is Node’s default (node or undici) and that send no x-sequenzy-client header receive only the three original events, without weekly_report, because Sequenzy CLI releases before 0.0.124 crash on events they do not know. Set any User-Agent or x-sequenzy-client: your-app/1.0 to get the full list. This shim will be removed once those CLI versions are retired.

Request

array
required
Preferences to set. Must contain at least one entry.
string
required
new_subscriber, form_submitted, campaign_completed, or weekly_report.
string
required
off, instant, daily, or weekly. daily is not valid for form_submitted or campaign_completed - each submission and each campaign finish is its own event, so there is nothing to roll up. weekly_report accepts only off and weekly.

Responses

Before a bulk import

You do not need to turn notifications off before importing contacts. Imports never trigger new-subscriber notifications, and a high-volume day of real signups automatically falls back to a daily summary. See Account Notifications.