Sender field requirements for Email activities

As we make changes to our API, we’ll publish below. Changes to the product itself will be published on Product Updates.

We fixed a bug in the Email API that previously allowed creating emails without a sender in cases where a sender is required.

The sender field is required for emails with status inbox, scheduled, outbox, or error. It may be omitted in the following cases:

For draft, since the sender can be specified later before sending.
For sent, where it defaults to the email address of the user associated with the email or the owner of the API key.

When updating a draft’s status to scheduled or outbox, the sender field is now required if the email doesn’t have one yet.

As we make changes to our API, we’ll publish below. Changes to the product itself will be published on Product Updates.

We fixed a bug in the Email API that previously allowed creating emails without a sender in cases where a sender is required.

The sender field is required for emails with status inbox, scheduled, outbox, or error. It may be omitted in the following cases:

For draft, since the sender can be specified later before sending.
For sent, where it defaults to the email address of the user associated with the email or the owner of the API key.

When updating a draft’s status to scheduled or outbox, the sender field is now required if the email doesn’t have one yet.

API Changelog