The visible link is guaranteed
Use the unsubscribe merge tag in HTML or text. If it is absent, NoticeAPI appends a plain unsubscribe footer before delivery.
One-click unsubscribeThe opt-out path is
The opt-out path is
already in the send.
Broadcasts and automations carry a visible unsubscribe link, RFC 8058 headers, and a signed hosted endpoint. The next audience send checks the preference again before delivery.
NoticeAPI enforces the in-product opt-out path. Senders still own consent collection, message classification, and preferences held in other systems.
Audience preference[email protected]Enforced
01MessageVisible unsubscribe URL
02MailboxRFC 8058 one-click headers
03Project stateMarketing opt-out recorded
04Next audience sendRecipient skipped before delivery
Click to durable state
Follow one opt-out through the send path.
The link, mailbox headers, state change, and pre-send guard all refer to the same project and recipient.
One-click headers travel with it
Broadcasts and automation steps add List-Unsubscribe plus List-Unsubscribe-Post: List-Unsubscribe=One-Click.
The signed POST changes state
The hosted endpoint verifies the HMAC token, records a project marketing opt-out, and marks matching contacts unsubscribed.
Later audience sends check again
Broadcast workers re-read contact and suppression state. Due automation steps cancel when the contact opted out or is suppressed.
Separate the states
An unsubscribe and a suppression are not the same record.
Both can stop audience delivery, but they describe different recipient decisions and different operational risks.
Compare suppression behaviorStops audience email in the project
An unsubscribe applies to that address across the project’s audiences. Re-importing the address does not silently restore subscribed state.
Checked by broadcasts and automationsStops the provider handoff
Bounce, suppression, quarantine, FilteredSpam, and manual records create a separate project-scoped delivery block.
Checked by audience and transactional pathsReceipts are not marketing subscriptions
A marketing opt-out does not change transactional sending. A delivery suppression still blocks the recipient before provider handoff.
Keep promotional content on audience sendsRFC 8058 path
One-click for providers. Confirmation for people.
The visible email link opens a confirmation page with GET. A mailbox provider uses POST for one-click unsubscribe. The endpoint verifies the signed token, applies the preference without a login, and returns a completed state.
A malformed token is rejected. Requests are rate limited, and a repeated valid opt-out remains idempotently unsubscribed.
Outbound audience messageHeaders
List-Unsubscribe<https://noticeapi.com/api/unsubscribe?…>List-Unsubscribe-PostList-Unsubscribe=One-ClickGETHuman confirmationPOSTMailbox one-clickSTATEProject opt-out
The consent boundary
NoticeAPI enforces the path. You own the permission.
Product controls prevent a stored opt-out from being ignored. They do not create consent or synchronize every external system your team uses.
NoticeAPI enforces
- A visible unsubscribe link on audience messages
- RFC 8058 headers on broadcasts and automation steps
- A signed endpoint and project-wide marketing opt-out
- Contact and suppression checks before later sends
The sender owns
- Evidence of consent and accurate message classification
- Truthful sender identity and required sender information
- Opt-outs held in any other sending or customer system
- A dedicated, documented re-opt-in before restoring access
Complaints follow the suppression path.Provider FilteredSpam outcomes are recorded as spam events and create a delivery suppression. That block is distinct from a recipient’s marketing unsubscribe.Read the rules
Build against the behavior
The docs behind each boundary.
Broadcast docsCreate, schedule, and send to subscribed audience contacts.Automation docsRun lifecycle steps that stop on unsubscribe or suppression.Audience docsManage contacts, merge fields, and subscription state.Suppression docsReview project delivery blocks and confirmed re-opt-in rules.Acceptable useRead the consent and sender responsibilities behind every audience.
Audience email with a stop condition
Build broadcasts and automations that honor opt-outs.
Start with a subscribed audience, send through the marketing path, and let the same project state guard every later step.