May 2026

Audience Over The API

Contacts, lists, segments, topics and properties are now fully addressable over the REST API rather than merely readable.

Lists, segments, topics and properties gained create, update and delete; contacts gained update and bulk create; and a contact can be attached to or detached from a list or a topic, singly or in bulk. Writes need the audience:write scope and reads audience:read.

Three nested endpoints were removed in favour of filters on the collection routes. GET /audience/lists/{id}/contacts and GET /audience/segments/{id}/contacts become GET /audience/contacts?list_id= and ?segment_id=, and GET /audience/lists/{id}/segments becomes GET /audience/segments?list_id=.

The contacts list envelope changed with them, from {contacts, total, page, per_page} to {contacts, pagination: {…}}, and a contact's embedded lists no longer carry contacts_count. If you integrated before May, those three things are what will break; read them before you upgrade.

Campaigns Over The API

A campaign can be listed, read, sent, scheduled, rescheduled and unscheduled from code, with its events and stats readable back.

Six endpoints ship behind two new scopes, campaigns:read and campaigns:write. Every campaign carries a stats object — injections, deliveries, bounces, complaints, opens, unique opens, clicks, unique clicks and unsubscribes — read from the same figures the app shows. The events endpoint is cursor-paginated and filters by event type, recipient, and date range.

Scheduling is idempotent: a draft can be scheduled and an already-scheduled campaign moved to a new time. Sending immediately still requires a clean draft, and a campaign with a schedule pending says so and points at the unschedule endpoint rather than returning a vague refusal.

Note what is not here: there is no endpoint that creates a campaign or attaches an audience to one. A campaign is still composed in the app, and the API drives it from there.

Every Marketing Send Carries A Working Unsubscribe

Campaigns now go out with an unsubscribe link and one-click headers whether or not anyone remembered to add the tag.

When neither {{unsubscribe_link}} nor {{unsubscribe_url}} appears in your HTML, a minimal footer is appended at render time — not at save time, so your stored template stays exactly as you wrote it. Every campaign also sets List-Unsubscribe and List-Unsubscribe-Post, so the one-click button works in Gmail and Apple Mail without you touching a template.

There is no way to switch this off, and that is deliberate. The only way to avoid the default footer is to place your own unsubscribe tag, which is then left alone. The editor warns you before you save an email that has neither. Mailbox providers tighten these rules every year; treat it as table stakes rather than a feature.

The Unsubscribe Page Asks Why, And Offers A Way Back

Clicking the link in the body used to unsubscribe you the moment the page loaded. It now asks first.

The page offers a reason — too many emails, not relevant, never signed up, or something you type — and unsubscribing takes a deliberate action. Afterwards it offers a one-click way back, because a good share of those clicks are accidents and there is no reason to make them permanent. The reason is recorded on the contact's history.

The one-click header path is untouched and still unsubscribes immediately, as the specification requires.

A Browser-Readable Copy Of Any Campaign

{{webversion_link}} gives every recipient their own “view in browser” link.

The page re-resolves that recipient's own merge data and renders the campaign, so what they see in a browser matches what landed in their inbox. Send time and view time share one code path, so the two cannot drift apart. The tag sits next to {{unsubscribe_link}} in the editor.

Recipient-Facing Pages In The Recipient's Language

The unsubscribe and web-version pages went from English only to 19 languages over the course of the month.

Language resolves per recipient: the contact's own communication language first, then a team-level default you set in settings, then English. Only the surrounding page is translated — the email inside it is your content and is left alone.

Arabic and Hebrew were deliberately left out for now, because these pages have no right-to-left handling yet and shipping them half-done would be worse than not shipping them. Unsubscribe reasons are stored as stable keys rather than as the translated label the recipient happened to see, so the data stays comparable across languages.

Sensitive Actions Are Gated For SSO Users Too

Signing in with Google or GitHub used to switch off re-authentication entirely for everything behind it.

Changing your password, changing your account email, turning two-factor on or off, deleting your user and deleting a team all went through with no second check for anyone holding an OAuth identity. That is now closed: SSO users get a six-digit code by email, valid for ten minutes, and one verification opens a fifteen-minute window across the gated actions. Password users are unchanged and still confirm with their password.

Changing your account email also now genuinely re-sends the verification email. It used to mark you unverified and give you nothing to click.