Skip to content
Docs

Reference

Webhooks changelog

Changes to Webhooks: new features, improvements and fixes.

October 2026

  1. New

    Segments in alpha

    SegmentsCampaignsAutomationsWebhooks

    Segments are now under Email Marketing > Segments in the dashboard. They’re in alpha: open only to the Emailit team while we test them, so customer workspaces don’t see them yet. A segment starts from all contacts or the subscribers of chosen audiences, and narrows them down with groups of rules on contact fields, custom fields and audience membership. Emailit evaluates it whenever it’s counted, listed or sent to, so it’s always current.

    • Campaigns can send to segments, alone or with audiences, and exclude audiences and segments. Exclusions now apply when the campaign sends. If an excluded audience or segment was deleted, Emailit doesn’t send the campaign.
    • Tracked segments on Pro, Business and Custom also record who joins and leaves. Joins and leaves start automations with the new Added to segment and Removed from segment triggers, send the segment.contact_added and segment.contact_removed webhook events, and fill the segment’s Growth chart. You choose tracking when you create a segment.
    • Limits: Pay as you go includes 3 segments, Pro 10 and Business 100, tracked or not. On Custom plans the number is flexible.
    • API and MCP: the Segments API and the segments MCP toolset create, preview and list segments, their contacts and their growth.

    See Segments and Tracked segments.

  2. New

    Event tracking: workspace and custom events

    Event trackingAPI keysWebhooks

    You can now send your own events next to the ones Emailit records, such as an order, a plan change or a product view. They’re on the new Workspace events and Tracking tabs of Email API > Events.

    • Two scopes. Workspace events (w:<name>) are declared first with typed properties, and Emailit rejects events that don’t match. Custom events (c:<name>) take any JSON object. The event log has a Scope filter, and the List events API a scope parameter.
    • From your servers. Send an event records one event, and Send events in a batch up to 100. They work with the new Events Only API keys, which can send events but can’t read data or send email.
    • From your website. The tracking script sends events with a public tracking key that you can limit to your own sites. identify ties a visitor’s events to a contact.
    • Contacts and webhooks. Events show in the contact’s Activity log. Webhooks receive the types you pick, or every workspace or custom event with w:* and c:*.
    • API and MCP. The Workspace events and Tracking keys APIs, and the send-event and workspace event tools in the events MCP toolset.
    • Plans. Event tracking and the tracking script are included with Pro, Business and Custom plans. Pro can use 100 event types, Business 1,000, and Custom has no limit. See Limits.

    See Event tracking.

  3. Changed

    Unlimited sending domains on Pro and Business

    Sending domainsBilling & creditsWebhooksSuppressions

    Plan limits now match the pricing page:

    • Sending domains. Pro, Business and Custom have no domain limit (before: 100 on Pro, 1,000 on Business). Pay as you go is unchanged: no limit after the first credit purchase, 3 domains before it.
    • Webhook endpoints. Custom plans have no fixed limit. Pay as you go keeps 3, Pro 10 and Business 100.
    • Automatic suppression. Custom plans can change it in Workspace > Settings, like Pro and Business.
    • Domain review. Domains registered less than 30 days ago are only reviewed on Pay as you go.

    See Domain limits and Limits and quotas.

  4. Fixed

    email.held in the webhook event picker, test events and MCP

    WebhooksMCP server

    email.held already reached webhooks with All events on, but it was missing elsewhere: the Events picker, the Send test dialog and the event filter on the Events page didn’t list it, Send a test event returned 400 “Unknown event type”, and the MCP create-webhook, update-webhook and test-webhook tools rejected it. All of them accept it now.

    See email.held and Set up a webhook.

September 2026

  1. Changed

    Subscriber and webhook limits per plan

    AudiencesWebhooksLimits & retention

    Limit Pay as you go Pro Business
    Subscribers per audience 10,000 50,000 250,000
    Webhook endpoints 3 10 100
    Webhook payload filters Not available Available Available

    Custom plans have no subscriber limit. The subscriber limit applies when you add subscribers, import contacts, use an audience’s subscribe URL and run automations. Creating a webhook above your limit returns 422, and the Audiences and Webhooks pages show how much of each limit you use.

    On Pay as you go, setting a payload filter returns 403 with plan_required, and existing filters are ignored. See Limits.

  2. New

    Webhook filters, test events and manual retries

    Webhooks

    • Send test delivers a sample payload for any event type to your endpoint.
    • Payload filters deliver only the events whose data matches up to 25 rules.
    • Webhook secret resets the signing secret.
    • Failed requests are retried after 5 minutes, 30 minutes, 2 hours and 5 hours, then every 12 hours, up to 11 attempts. Emailit emails the workspace owner when an endpoint keeps failing and disables it after 3 days of continuous failures.
    • Retry failed re-queues the failed requests from the last 7 days and re-enables the webhook. You can also retry a single request.

    See Webhooks and Retries and failures.

May 2026

  1. New

    Spam complaints from feedback loops

    DeliverabilitySuppressionsWebhooks

    When a recipient marks your email as spam and their provider reports it through a feedback loop, Emailit matches the report to the original email, sets its status to complained and sends an email.complained event. The address is added to your suppression list as a complaint, so you don’t email it again.

    See Bounces and complaints.

February 2026

  1. New

    Webhooks v2

    Webhooks

    Every request is signed with your webhook secret. To verify one, compute an HMAC-SHA256 of the X-Emailit-Timestamp value, a dot and the raw body, and compare it with the X-Emailit-Signature header. Subscribe to specific event types or to all events. Failed deliveries are retried automatically.

    See Webhooks for the current payload format and retry schedule.

  2. Changed

    Simplified email statuses

    Email logsEmail APIWebhooks

    Old status New status
    pending accepted or scheduled
    sent delivered
    softfail attempted
    hardfail bounced
    opened loaded
    error failed

    Existing emails and deliveries were migrated to the new names. Events and webhook requests created before the change keep the values they were sent with. See Email statuses for the current list.

  3. New

    Inbound email

    Inbound emailWebhooks

    Add an MX record for inbound.yourdomain.com that points to inbound.emailitmail.com with priority 10. Emailit accepts mail for any address on that subdomain and sends an email.received event with the sender, recipient, subject and email ID. Fetch the full message with Retrieve an email.

    Each received email costs 1 credit. See Set up inbound email.

  4. New

    Contacts, Events and Webhooks APIs

    ContactsEmail logsWebhooksREST API

    • Contacts: create, list, retrieve, update and delete contacts. Look a contact up by its con_ ID or email address, and add it to audiences in the same call.
    • Events: list events, filtered by one or more types and optionally with their data, and retrieve a single event.
    • Webhooks: create, list, retrieve, update and delete webhook endpoints.

    These endpoints need a full access key. See the API reference.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.