Email API changelog

The Retry button on a held email now works, and Retry an email accepts emails with the status held. Fix the reason the email was held first, for example a high spam score or missing credits, then retry it.

A retry creates a new email with a new ID and costs credits like any other send. Emails older than 30 days, or whose content was removed by data retention, can’t be retried. See Retry and forward.

Emailit compares the addresses in Reply-To and From, ignoring display names and letter case. When they’re the same, it removes Reply-To before signing the message. Replies still reach the From address.

When the addresses differ, Reply-To is kept unchanged. See Email headers.

• The API and SMTP match the From domain without regard to letter case, so ada@Acme.com sends from the verified domain acme.com.
• Changing a domain’s tracking or inbound subdomain in the dashboard, or with tracking_key and inbound_key in Update a domain, now saves the new value. Publish the DNS record for the new name and verify it.

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

A send request with tracking turned on used to fail with 422 when the sending domain had no verified tracking CNAME. Emailit now accepts the email and sends it without rewriting links or adding the open pixel.

To track opens and clicks, publish the tracking CNAME record for your domain and verify it. See Custom tracking domain.

Temporary failures were recorded on the delivery, but the email kept its earlier status. The email itself now moves to attempted while Emailit retries, so the emails list and the API show which emails are delayed.

Later statuses, such as delivered, and final statuses aren’t overwritten. See Email statuses.

• Compose on the Emails page, or in Quick Actions on the dashboard, sends a one-off email from a verified domain, for example to test your setup. Under Advanced you can attribute the send to an API key. Compose allows 3 emails per minute and 10 per hour per workspace. See Compose.
• Cancel delivery pulls an accepted, scheduled or attempted email from the queue. Cancellation is best effort: an email that’s already being handed to the recipient’s server may still be delivered. See Cancel an email.

Select Forward on an email’s detail page, or call Forward an email with a to address. By default the recipient gets a plain copy. Turn on the forwarded headers and add a comment if you want to give context.

A forward is a new email: it costs credits and counts toward your sending limits. You can forward 3 emails per hour per workspace. See Retry and forward.

The sandbox rule now applies to the API, SMTP, Compose, retries, automations and campaigns. Sending to anyone else returns 403 with the code unverified_workspace_recipient from the API and 550 from SMTP, and campaign sends are blocked. Workspaces with production access aren’t affected.

To lift the restriction, verify a domain and request production access.

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.

• List emails: GET /v2/emails
• Retrieve raw MIME: GET /v2/emails/:id/raw
• Retrieve the body: GET /v2/emails/:id/body
• Retrieve metadata: GET /v2/emails/:id/meta
• List attachments: GET /v2/emails/:id/attachments

These endpoints need a full access key. Content is available until your plan’s data retention period removes it.

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.

Build templates with the HTML editor, the rich-text editor or the Dragit drag-and-drop editor. Templates that share an alias are versions of one template, and only the published version is used when you send by alias.

Manage templates with the Templates API, and send one by passing template and variables to Send an email. See Templates.

Retry duplicates the original email, gives the copy a new ID and sends it through the normal pipeline. It’s billed like any new email. To retry from code, call Retry an email.

• Send an email: each recipient gets its own email ID. Schedule with an ISO 8601 date, a Unix timestamp or natural language such as “tomorrow at 9am”, and prevent duplicates with the Idempotency-Key header.
• Retrieve an email: status, headers, content, tracking settings and metadata.
• Update a scheduled email: change the send time up to 3 minutes before it’s due.
• Cancel an email: stop a scheduled or queued email.

Every send response includes ratelimit-* headers. See Rate limits.

Requests over the limit are rejected instead of queued, so configure your client to send at most 2 emails per second or to retry rejected sends. The change was rolled out to workspaces gradually.

See Rate limits.