---
title: "List Digests"
method: GET
path: "/api/v1/internal/release-email/digests"
tags: ["internal", "release-email"]
---

# List Digests

`GET /api/v1/internal/release-email/digests`

## Response `200`

Successful Response

- ReleaseEmailDigestResponse[]
  - `id` string, uuid, required
  - `month_start` string, date, required
  - `covers_start` string, date, nullable, required
  - `covers_end` string, date, nullable, required
  - `subject` string, required
  - `preheader` string, nullable, required
  - `body_markdown` string, 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_at` string, date-time, nullable, required
  - `updated_at` string, date-time, required
  - `sent_at` string, date-time, nullable, required
  - `recipient_count` integer, nullable, required
  - `resend_broadcast_id` string, nullable, required
  - `internal_test_broadcast_id` string, nullable, required
  - `internal_test_sent_at` string, date-time, nullable, required
  - `is_sent` boolean, required
  - `is_locked` boolean, required
  - `is_test_send_current` boolean, required

---

[API](https://skmtc.net/maia-analytics/apis/maia-api.md) · [All operations](https://skmtc.net/maia-analytics/apis/maia-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/maia-analytics/maia-api/versions/ba2b8d962161/schema)
