Emailit is a modern transactional and marketing email API launched to compete with Postmark, SendGrid, and Mailgun on developer experience, pricing, and modern SDKs. The unsubscribe mechanism uses the {{unsubscribe_url}} merge variable in email templates, and Emailit handles RFC 8058 compliance automatically for marketing sends from authenticated domains. Transactional API sends require manual header injection via the headers parameter. Suppression is tracked per Message Stream, matching the Postmark model of segregating transactional and marketing suppressions. This guide covers the tag, the streams model, and how to verify the setup end to end.
Emailit unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in Broadcast footer, manual for transactional API |
| Scope | Per Message Stream suppression |
| Config path | Dashboard > Message Streams > Settings |
| RFC 8058 one-click | Yes for Broadcasts, manual header injection for transactional API |
How to add the unsubscribe tag in Emailit
Place the merge tag exactly as shown below in the email template. Emailit 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>Auto-embedded in Broadcast footer, manual for transactional API
Yes for Broadcasts, manual header injection for transactional API 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.
Emailit distinguishes Broadcast Streams (marketing sends with automatic RFC 8058 headers) from Transactional Streams (API sends where headers must be injected manually via the headers parameter). Sending marketing content through a Transactional Stream bypasses suppression and violates platform policy. Always classify streams correctly during account setup to avoid deliverability and compliance issues.
Testing your Emailit unsubscribe link
- Send a test message to a controlled Gmail address you own via the Emailit 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 Emailit unsubscribe link (step by step)
Emailit Broadcast Streams include the unsubscribe link in the default footer, but Transactional Stream API sends require the tag inserted manually and headers injected via the headers parameter.
- Open your Broadcast Stream template or API payload for Transactional sends in Emailit.
- Add or edit a text block in the footer (Broadcasts) or the API body (Transactional) where the unsubscribe link should appear.
- Insert the merge variable
{{unsubscribe_url}}. Emailit replaces it at send time with a signed URL scoped to the recipient. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - For Transactional Streams, add List-Unsubscribe headers via the headers parameter in the API call for RFC 8058 compliance if the send qualifies as marketing.
- Send a test to a seed address and verify the rendered link routes to the Emailit-hosted unsubscribe confirmation page.
Message Streams and suppression segregation
Emailit distinguishes Broadcast Streams (marketing sends with automatic RFC 8058 headers and preference center) from Transactional Streams (API sends where headers must be injected manually and unsubscribe is optional). Sending marketing content through a Transactional Stream bypasses suppression and violates platform policy. Always classify streams correctly during account setup to avoid deliverability and compliance issues. This is the Postmark model applied to a modern API-first architecture.
RFC 8058 one-click headers
Emailit added RFC 8058 one-click unsubscribe automatically for Broadcast Streams from authenticated domains. The List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send. Transactional Stream API sends require manual header injection via the headers parameter if the send qualifies as marketing (defined by Google and Yahoo bulk-sender thresholds). Modern SDK examples in the Emailit docs demonstrate correct header injection for common transactional-marketing hybrid use cases like re-engagement emails.
Developer experience and modern SDKs
Emailit competes with Postmark, SendGrid, and Mailgun on developer experience: TypeScript-first SDKs, webhook management dashboards, and modern testing tooling (staging environments, replay tools, granular event webhooks). The API structure resembles Resend and Loops (modern DX-focused ESPs) more than legacy platforms. For teams migrating from SendGrid, the API surface is similar enough that migration typically takes a few hours per template.
Frequently Asked Questions
What is the Emailit unsubscribe tag?
The tag is {{unsubscribe_url}}. Emailit replaces it at send time with a signed URL scoped to the recipient. Use it inside an anchor: <a href="{{unsubscribe_url}}">Unsubscribe</a>.
What is a Message Stream in Emailit?
Message Streams segregate different types of sends (marketing broadcasts vs transactional API sends) with independent suppression lists and RFC 8058 defaults. This matches the Postmark model of preventing accidental unsubscribe bypass by routing marketing content through the wrong stream type.
Does Emailit support one-click unsubscribe for Gmail and Yahoo?
Yes for Broadcast Streams from authenticated domains. Emailit injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send. Transactional Stream sends require manual header injection via the API headers parameter.
Can I migrate from SendGrid to Emailit easily?
Yes typically. The Emailit API surface is similar to modern ESPs (Resend, Postmark, Loops) and migration from SendGrid usually takes a few hours per template. Suppression list export/import preserves opt-out history during migration.
Is Emailit suitable for high-volume marketing sends?
Yes for marketing volumes up to millions of sends per month via Broadcast Streams. For very high enterprise volumes (100M+ sends per month), evaluate dedicated IPs and enterprise SLA options. Emailit pricing is competitive with SendGrid and Postmark at scale.
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.
