Skip to content
Docs

Reference

API keys changelog

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

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.