Courier is a transactional and multi-channel notification API platform serving SaaS developers and technical teams with unified messaging across email, SMS, push, Slack, Teams, and Discord. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag placed in notification templates, and Courier emits RFC 8058 headers automatically for authenticated sending domains. Suppression is tracked at the recipient level via API. This guide covers the tag, the multi-channel notification model, and how to verify the setup end to end.
Courier Com unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Manual placement in notification templates |
| Scope | Recipient-level opt-out via API |
| Config path | Dashboard > Templates > Footer configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Courier Com
Place the merge tag exactly as shown below in the email template. Courier Com replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribe_url}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribe_url}}">Unsubscribe from this list</a>Manual placement in notification templates
Yes, automatic for authenticated sending domains The recipient's mailbox provider (Gmail, Yahoo) uses the List-Unsubscribe-Post header to expose the native one-click button on the message. Requires domain authentication with DKIM and DMARC.
Courier multi-channel notification API design routes messages to email, SMS, push, or chat based on user preferences and availability. Preference management is per-channel and per-notification-type by default, giving users granular control. Configure notification categories carefully to distinguish transactional (order confirmations bypass opt-out) from marketing (promotional broadcasts respect opt-out) per most jurisdictions.
Testing your Courier Com unsubscribe link
- Send a test message to a controlled Gmail address you own via the Courier Com campaign preview action
- Click the footer unsubscribe link and confirm the opt-out on the landing page
- Check the subscriber or contact record: the status should be Unsubscribed within seconds
- Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for
List-UnsubscribeandList-Unsubscribe-Post: List-Unsubscribe=One-Click
Want the full 222-platform reference?
See the pillar guide with the compliance landscape, the RFC 8058 deep dive, and the unsubscribe tag for every ESP: How to add an unsubscribe link: the complete 2026 guide →
How to add the Courier unsubscribe link (step by step)
- Open your template in the Courier dashboard.
- Add or edit a text block in the email footer.
- Insert the merge tag
{{unsubscribe_url}}. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - Configure the sender identity under Dashboard > Templates > Footer configuration.
- Send a test to a seed address and verify the rendered link routes to the Courier-hosted preference page.
Multi-channel notification API design
Courier multi-channel notification API design routes messages to email, SMS, push, or chat based on user preferences and availability. Preference management is per-channel and per-notification-type by default, giving users granular control. Configure notification categories carefully to distinguish transactional (order confirmations bypass opt-out) from marketing (promotional broadcasts respect opt-out) per most jurisdictions. Slack, Teams, and Discord integrations expand notification reach to workplace chat platforms.
RFC 8058 one-click headers
Courier added RFC 8058 one-click unsubscribe automatically ahead of the Google and Yahoo February 2024 requirements. The List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing-classified email send from domains authenticated under Dashboard > Templates. SPF and DKIM records must be verified. Transactional email sends omit unsubscribe headers per RFC 8058 recipient-level scoping.
Developer experience and preference management
Courier developer experience emphasizes JSON-based API workflow with typed SDK support for Node.js, Python, Ruby, Go, and other common languages. Preference management via API lets applications sync user notification preferences with customer databases in real time. Route rules determine which channel to prefer for each notification type based on user preferences, delivery success rates, and time-of-day.
Frequently Asked Questions
What is the Courier unsubscribe tag?
The merge tag is {{unsubscribe_url}}. Courier replaces it at send time with a signed URL scoped to the recipient.
Does opt-out apply across all channels?
Per-channel and per-notification-type by default. Users can opt out of marketing email while continuing SMS transactional alerts. Configure unified suppression only when business expectations require it.
Does Courier support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains on marketing-classified email sends. Courier injects List-Unsubscribe and List-Unsubscribe-Post headers.
Which channels does Courier support?
Email, SMS, push (iOS/Android), Slack, Microsoft Teams, Discord, and other chat platforms via provider integrations.
How does Courier compare to Sidemail or Postmark?
Sidemail and Postmark focus on transactional email. Courier expands to multi-channel notifications including chat platforms. Vendor choice depends on channel scope needed.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
