Get Email Events
The delivery timeline for a single email: an ordered list of { type, timestamp } entries covering pending, sent, delivered, opened, clicked, bounced, complained, suppressed, and delivery-delayed. Types can repeat: a recipient who opens twice produces two opened entries.
Authorization
Authorization In: header
Path Parameters
ID of the project that owns the campaign.
ID of the campaign the email belongs to.
ID of the email whose events to return.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://www.saasco.com/api/v2/projects/string/email-campaigns/string/emails/string/events"[
{
"timestamp": "string",
"type": "pending"
}
]{
"code": "BAD_REQUEST",
"message": "Invalid input data",
"issues": []
}{
"code": "UNAUTHORIZED",
"message": "Authorization not provided",
"issues": []
}{
"code": "FORBIDDEN",
"message": "Insufficient access",
"issues": []
}{
"code": "NOT_FOUND",
"message": "Not found",
"issues": []
}{
"code": "INTERNAL_SERVER_ERROR",
"message": "Internal server error",
"issues": []
}List Contact Emails
Every email this project has sent to one contact, across all campaigns: the per-person send history you would show on a contact detail page. Use List Emails instead to work from the campaign side.
Get Sender Status
Reports whether the project is currently allowed to send email. Saasco blocks sending for projects with poor deliverability or abuse signals; when blocked, `canSend` is false and `statusReason` explains why. Send Email Campaign and Send Test Email both enforce this, so check it before offering a send action in your own UI.