API
Weekly digest posts on the API
GET /digest-posts returns the posts from digest editions that have already gone out, so you can republish your internal newsletter on an intranet or a portal.
Last updated September 2, 2026
GET https://api.gorilladash.com/api/v1/digest-posts returns the individual posts that make up your weekly digest — the newsletter you send around your network. Use it to build an archive page, or to surface the latest few items on an intranet.
Parameters
| Parameter | Notes |
|---|---|
page | Page number, from 1. |
results_per_page | Up to 100. Defaults to 25. |
Posts come back newest published first.
What comes back
| Field | Notes |
|---|---|
id, organisation_id | Key your own records on id. |
heading, sub_heading | The post title. |
author | Who wrote it. |
article | The body. |
position | Where it sat within its edition. |
publish_date | When it was published. Can be empty on older posts. |
card_image | The post image. |
What counts as published
A POST IS PUBLIC ONCE ITS EDITION HAS GONE OUT
Publication is recorded on the digest edition, not on the post. A post you have written but not yet included in a sent edition will not appear here, however finished it looks in Gorilla Dash. If a post is missing, check the edition it belongs to.
Scoping and caching
Digest posts belong to the organisation — there is no per-tribe digest — so a tribe key sees its parent organisation's posts. The endpoint is cached and sends an ETag.