Trust

How NoticeAPI Handles Unsubscribe Requests

NoticeAPI treats unsubscribe handling as part of the send path, not a checkbox left for every app to rebuild. Broadcasts and automations carry working unsubscribe links, one-click headers, contact state, and delivery events.

Start free Read broadcast docs

Consent

Unsubscribe handling is enforced for audience sends.

Transactional email and consent-based audience email share one platform, but audience sends keep their consent rules: unsubscribe, List-Unsubscribe, suppressions, and subscription state.

Flow

What happens when someone opts out.

1

The message gets an unsubscribe path

Broadcasts and automations can use the unsubscribe merge tag. If the tag is missing, NoticeAPI can append a footer link automatically.

2

Headers are added for one-click unsubscribe

Marketing sends include List-Unsubscribe and List-Unsubscribe-Post headers so mailbox providers can expose a native unsubscribe action.

3

The token updates contact state

The hosted unsubscribe endpoint verifies the signed token, marks the contact unsubscribed, and records an unsubscribe event.

4

Future audience sends skip the contact

Broadcasts and automations check subscribed and suppression state before sending future lifecycle or marketing email.

Implementation links

Build audience sends with the right guardrails.

Broadcast docsCreate drafts and send to subscribed audiences.Automation docsBuild template sequences that stop on unsubscribe.AudiencesManage contacts, merge fields, and subscription state.Acceptable useConsent rules for NoticeAPI sending.