A send run finished handing every recipient to the email provider, and
the run was stamped with the completed_at this payload carries.
This is the dispatch milestone, not the delivery milestone. It says the
provider accepted the messages; whether they landed in inboxes is what
the delivery.* topics report, and those arrive later and one per
recipient.
Named for the send, not for the article. A send run is its own resource
in the REST catalog (/sends), it carries its own id, and one article
can have several across retries, so the topic sits in the send namespace
alongside send.failed rather than under article.*. data.article_id
is still there for anyone routing by article.
Delivered as a single HTTPS POST to the consumer's registered endpoint, with the message as the JSON request body. Respond 2xx to acknowledge. Anything else, or a timeout, is retried with backoff, so acknowledge fast and do the work afterwards.
Headers
-
API version the payload conforms to. Same value as
api_versionin the envelope. -
Same value as
idin the envelope. The dedupe key. -
Same value as
typein the envelope. The topic name. -
HMAC over the raw request body. Verify before parsing.
-
Unix seconds the signature was produced at. Reject anything outside your tolerance window.
-
1 on the first attempt, incremented on each retry. Informational only. A consumer must be idempotent regardless of its value.
Minimum value is
1.
Body
Required
A send run finished handing every recipient to the provider.
-
Unique id for this event. Stable across redeliveries, so it is the dedupe key. It is the primary key of the row the publisher wrote, which means it is assigned when the state change is recorded, not when the message is dispatched.
-
The topic name, identical to the channel address. Route on this.
Value is
send.completed. -
The
Commune-Versionvalue this payload conforms to. Present on the message itself, not only on the request header, so an event persisted to a consumer's own store stays self-describing. -
RFC 3339 timestamp of the state change, not of the delivery attempt. Use it to order events, since delivery order is not guaranteed.
-
Who caused the change. ALWAYS
nulltoday and consumers must treat it that way: the public API is currently read-only, so nothing that reaches this catalog was triggered through it, and Commune does not backfill an actor for changes made in the product UI or by a cron. The field exists now so that populating it, once writes exist, is an additive change rather than a new envelope version.Additional properties are NOT allowed.
-
ALWAYS
nulltoday. Once the public API accepts writes this carries theIdempotency-Keyheader of the write that caused the change, so a consumer can tie an event back to its own request and collapse the duplicates a retried write would otherwise produce. Null stays a legitimate value even then: a change made in the product UI or by a cron has no originating request to key on.Maximum length is
255. -
Event-specific body. Narrowed by each concrete event schema below.
Responses
-
The consumer accepted the delivery. Any 2xx acknowledges the message and it is not sent again.
-
The consumer rejected the delivery. Handled exactly like a 5xx: the message is retried with backoff, because a rejection cannot be told apart from a consumer that is briefly misconfigured.
-
The consumer failed to handle the delivery. Retried with backoff. A timeout is the same case and is retried too.
{
"id": "018f2a90-2222-7000-8000-000000000002",
"type": "send.completed",
"api_version": "2026-08-26",
"occurred_at": "2026-08-26T09:32:11Z",
"newsletter_id": "7d3f1c02-58a1-4a4e-9a0b-2f6d1c9e4411",
"actor": null,
"idempotency_key": null,
"data": {
"article_id": "4c9e2f81-0b7a-4d13-8e55-1a2b3c4d5e6f",
"send_id": "9a8b7c6d-5e4f-4a3b-2c1d-0e9f8a7b6c5d",
"started_at": "2026-08-26T09:28:40Z",
"completed_at": "2026-08-26T09:32:11Z",
"recipient_count": 540,
"sent_count": 538,
"failed_count": 2
}
}