Email activity
During beta, inspect individual sends and their events through the API. There is no global activity list or email detail screen in the dashboard.
Create credentials in Settings → Developers. Use GET /v1/workspaces/{workspaceId}/emails to list sends and GET /v1/workspaces/{workspaceId}/emails/{id} to inspect one, with the emails:read permission. The list supports purpose, contactId and submissionStatus filters.
To read recorded events, use GET /v1/workspaces/{workspaceId}/emails/{id}/events with both emails:read and events:read. See Sending email for the API contract, Authentication for request credentials and API conventions for pagination.
Read the send status
The API’s submission.status and delivery events describe different stages.
| Status | Meaning |
|---|---|
queued |
Sendiro accepted the email for processing. |
sending |
A submission attempt to the transport is in progress. |
retry_scheduled |
Another submission attempt is scheduled. |
submitted |
The transport accepted the send; this does not yet prove delivery to the recipient. |
submission_unknown |
The attempt’s outcome could not be established with certainty. |
failed |
A send failure was recorded. |
suppressed |
An applicable check blocked the send. |
An email accepted by Sendiro is not the same as a delivered email, and a delivery event does not prove that the recipient read it.
Read the details and events
The email response includes the sender, recipient, submission state and acceptance time. The delivery property retains available delivery observations; a failed submission includes a sanitized error.
The event endpoint returns recorded deliveries, bounces, spam complaints and other outcomes. API timestamps use UTC.
Events depend on the available transport. Local tests can simulate them and do not prove receipt in a real inbox.
Investigate before repeating
If the status is submission_unknown, do not repeat the send as though it had failed: the transport might have accepted it even though its response was not received.
Review details, events and the original operation’s outcome. To investigate with your team, retain the send identifier, workspace and UTC time. Do not share API keys or full recipient details unless they are needed.
For suppressed or failed emails, check senders, the product and available capacity. Marketing also checks consent and unsubscribe status.
Send a transactional email
Use POST /v1/workspaces/{workspaceId}/emails from your backend as described in Sending email. Retain the accepted email’s identifier to query its status and events.
Sending requires the applicable permissions, product capacity and an authorized sender. In a simulated environment it tests the flow within Sendiro, not real delivery.