Reference
API keys changelog
Changes to API keys: new features, improvements and fixes.
September 2026
Fixed
API v2 compatibility fixes
REST APIAPI keysEmail APISending domains
- API keys created before keys had the
secret_prefix are accepted on/v2again. - Retrieve an email returns the full email object, including
object,fromandto. - Domain responses return
track_loadsandtrack_clicksas0or1, as documented.
- API keys created before keys had the
Changed
Sending-only API keys limited to send endpoints
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
New
API v2
REST APIAPI keysSending domainsAudiencesSuppressions
API keys replace credentials. A key has the
fullorsendingscope, 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.