Notification Preferences
Get Notification Preferences
Get your account notification settings for the current company
GET
Get Notification Preferences
Get which account notifications Sequenzy emails you about this workspace: when a contact joins, when a form is submitted, when a campaign finishes sending, and the Monday weekly report.
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.
These are per-person settings. This endpoint always acts on the API key’s own user, and there is no way to read a teammate’s preferences through the API.
This endpoint requires the
See Account Notifications for when each notification fires and how the daily cap works.
account:read scope.
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
Response fields
array
Every notification event with its current mode. Events you have never
configured report the platform default rather than being omitted, so the array
always has one entry per event.
string
new_subscriber, form_submitted, campaign_completed, or weekly_report.string
off, instant (one email per occurrence), daily (one summary per day), or
weekly (one report per week).object
Modes each event accepts, keyed by event.
form_submitted and
campaign_completed do not accept daily; weekly_report accepts only off
and weekly.object
Mode each event uses when you have never configured it. Resolved for your
role: the workspace owner gets
weekly_report as weekly, invited members
get off until they opt in.