pub struct UpdateEmailMessageStatusDto {
pub events: Option<EmailEventsDto>,
pub recipients: Vec<UpdateRecipientMessageStatusDto>,
pub status: String,
}conversations only.Expand description
Request body to update the delivery status of an email message. status is required.
events and recipients are optional and may be included together with status. - Use
events to report aggregate delivery metrics (delivered count, open count, etc.). - Use
recipients to track per-recipient delivery outcomes for multi-recipient emails. - Use
status to set the overall message status. Multiple calls are additive — event counters
are merged, recipient statuses are upserted, and the message status is overwritten.
Fields§
§events: Option<EmailEventsDto>Aggregate delivery event counters. Counters are merged into existing values. The API
automatically infers related events (e.g., reporting clicked will also set opened
and delivered if not already present). See the endpoint description for the full
inference rules.
recipients: Vec<UpdateRecipientMessageStatusDto>Per-recipient delivery statuses. Each entry maps a recipient email address to a delivery status. Entries are upserted — if a recipient already has a status, it will be overwritten with the new value.
status: StringThe overall status of the email message. Required on every request. For emails with
multiple recipients, consider using the recipients array for granular tracking and
this field for the aggregate status.
Allowed values: pending, scheduled, sent, delivered, read, undelivered,
connected, failed, opened, clicked.
Required by the API.
Trait Implementations§
Source§impl Clone for UpdateEmailMessageStatusDto
impl Clone for UpdateEmailMessageStatusDto
Source§fn clone(&self) -> UpdateEmailMessageStatusDto
fn clone(&self) -> UpdateEmailMessageStatusDto
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more