Automations

Per-node aggregate of an automation

How many contacts went through each step, how many were skipped and how many failed, plus enrollments by status. For each step that sends: absolute numbers and email rates (human and non-human opens, clicks, content clicks), the most clicked links with their role and the attributed conversions. Answers the question of whoever designed the flow (at which step half of the people stop, and what they really click); to know what happened to ONE contact use the step log instead. A node with many skipped is the first place to look. ?since=<ISO> restricts to messages sent from that date, revenue included (orders attributed to those messages, whenever placed). revenue, overall and per node, is what the flow sold: orders attributed by the last click on the content, test runs excluded. Required scope: automations:read.

get/automations/{id}/stats

Request

  • Base URL: https://sending.dev/api/v1
  • URL: https://sending.dev/api/v1/automations/{id}/stats
  • Auth: HTTP bearer

Path parameters

idstring required

Automation ID.

Query parameters

sincestring

ISO 8601: only messages sent from this date.

attribution'first' | 'last'

Conversion model, last by default.

Response

Automation statistics.

idstring uuid required
namestring required
statusstring required
sincestring nullable required

Window applied to sent messages; null = all time.

attribution'first' | 'last' required
lastTestRununknown

Example response

{
  "nodes": [
    {
      "links": [
        {
          "firstClickAt": "2026-06-30T12:00:00.000Z",
          "lastClickAt": "2026-06-30T12:00:00.000Z"
        }
      ]
    }
  ],
  "links": [
    {
      "firstClickAt": "2026-06-30T12:00:00.000Z",
      "lastClickAt": "2026-06-30T12:00:00.000Z"
    }
  ],
  "conversions": {
    "recent": [
      {
        "occurredAt": "2026-06-30T12:00:00.000Z",
        "touchAt": "2026-06-30T12:00:00.000Z"
      }
    ]
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.