Skip to content
Docs

Reference

API keys changelog

Changes to API keys: new features, improvements and fixes.

October 2026

  1. 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.

September 2026

  1. Fixed

    API v2 compatibility fixes

    REST APIAPI keysEmail APISending domains

    • API keys created before keys had the secret_ prefix are accepted on /v2 again.
    • Retrieve an email returns the full email object, including object, from and to.
    • Domain responses return track_loads and track_clicks as 0 or 1, as documented.
  2. Changed

    Sending-only API keys limited to send endpoints

    API keysEmail API

    Sending-only keys could previously list and retrieve emails and call some other read endpoints. They’re now limited to Send an email and the actions on an existing email: reschedule, cancel, retry and forward. Other endpoints reject sending keys.

    If your integration also reads emails, domains or other resources, use a full access key for those calls. See API keys.

October 2025

  1. New

    API v2

    REST APIAPI keysSending domainsAudiencesSuppressions

    API keys replace credentials. A key has the full or sending scope, a sending key can be restricted to one sending domain, and you can manage keys through the API. API v1 stayed available while you migrated.

    See the API reference.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.