Trust
How NoticeAPI Handles Unsubscribe Requests
NoticeAPI treats unsubscribe handling as part of the send path. Broadcasts and automations carry working unsubscribe links, one-click headers, contact state, and delivery events.
Consent
Unsubscribe handling is enforced for audience sends.
Transactional and audience email share one platform, but audience sends keep their own enforcement path: unsubscribe links, List-Unsubscribe headers, suppressions, and recipient state.
Flow
What happens when someone opts out.
The message gets an unsubscribe path
Broadcasts and automations can use the unsubscribe merge tag. If the tag is missing, NoticeAPI appends a footer link automatically.
Headers are added for one-click unsubscribe
Audience sends include List-Unsubscribe and List-Unsubscribe-Post headers so mailbox providers can expose a native one-click action.
The token updates contact state
The hosted unsubscribe endpoint verifies the signed token, marks the contact as unsubscribed, and records the event.
Future audience sends skip the contact
Future broadcasts and automations check subscribed and suppression state before sending lifecycle or audience email.
One-click headers
How RFC 8058-style unsubscribe works.
Audience sends include List-Unsubscribe and List-Unsubscribe-Post. When a supporting mailbox provider performs one-click, it POSTs to the signed NoticeAPI unsubscribe URL with List-Unsubscribe=One-Click. NoticeAPI verifies the token, marks the contact unsubscribed, records an event, and skips that contact on future audience sends.
Compliance note
NoticeAPI handles the plumbing; senders still own consent.
One-click headers and hosted unsubscribe links help with mailbox-provider expectations for subscribed and promotional mail, but they do not replace your obligation to collect consent, identify yourself truthfully, keep recipient records current, and honor opt-outs across every system you use.
Implementation links