---
title: 'A collection''s newest weekly digest, with resolved release links'
description: >-
  The newest digest for the collection (highest weekStart), same body as GET
  /v1/collections/:slug/digests/:weekStart — one call instead of listing digests
  and then fetching the first week.
---
# A collection's newest weekly digest, with resolved release links

`GET https://api.releases.sh/v1/collections/{slug}/digests/latest`

The newest digest for the collection (highest `weekStart`), same body as `GET /v1/collections/:slug/digests/:weekStart` — one call instead of listing digests and then fetching the first week. Full digest row (title, intro, markdown body, cited release ids) plus server-resolved minimal release info (title, org, upstream url, product, canonical `/release/*` fallback path) for every cited release, and the body's parsed `###` sections (heading, anchor, lede, cited release ids, and those releases resolved) — resolved server-side so the web page never N+1s. `releases[].url` is the primary link when present; `path` is the fallback. Release ids that no longer resolve (deleted/suppressed since generation) are silently dropped from `releases` and `sections[].releases`.

**Auth:** optional Bearer token.

**Parameters**

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `slug` | path | string | yes | Collection slug. |

**Responses**

- `200` The newest digest row with resolved release links.
- `404` No collection with that slug, or the collection has no digests yet.

Full request and response schemas: [OpenAPI 3.1 spec](https://api.releases.sh/v1/openapi.json).