internal
release-email

Roll Up Pending

Changed on

Draft from a period's shipped work.

The period decides which entries are in scope; whether a digest already claimed one decides which of those are new. Repeating a claimed entry takes include_already_sent, so nothing is mailed twice by accident.

post/api/v1/internal/release-email/roll-up-pending

Request

  • Base URL
    https://api.maia-analytics.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.maia-analytics.com/api/v1/internal/release-email/roll-up-pending
  • Auth
    HTTP bearer

Request body

kind'week' | 'month' required
startstring date required
include_already_sentboolean

Response

Successful Response

idstring uuid required
month_startstring date required
covers_startstring date nullable required
covers_endstring date nullable required
subjectstring required
preheaderstring nullable required
body_markdownstring required
status'draft' | 'sending' | 'sent' required

Where a digest sits between editable and shipped.

SENDING exists so the claim on a send can be taken before Resend is called: the broadcast is the irreversible step, and a status that only changed after it returned would let a double click or a retry mail every customer twice.

last_test_sent_atstring date-time nullable required
updated_atstring date-time required
sent_atstring date-time nullable required
recipient_countinteger nullable required
resend_broadcast_idstring nullable required
internal_test_broadcast_idstring nullable required
internal_test_sent_atstring date-time nullable required
is_sentboolean required
is_lockedboolean required
is_test_send_currentboolean required

Changes