API
Blog articles on the API
GET /blog-articles and GET /blog-articles/{slug} — publish the blog you write in Gorilla Dash onto any website, with images and SEO metadata included.
Last updated September 2, 2026
Write your blog once in Gorilla Dash and read it out anywhere. GET https://api.gorilladash.com/api/v1/blog-articles lists your published posts, and GET /blog-articles/{slug} returns one in full.
Only published articles are ever returned. Drafts stay invisible, so you can write ahead without anything leaking onto a live site.
Listing posts
| Parameter | Notes |
|---|---|
page | Page number, from 1. |
results_per_page | Up to 100. Defaults to 25. |
tribe_slug | Only posts attached to one tribe. Organisation keys only. |
Newest first. The list is deliberately trimmed — heading, sub-heading, author, abstract, slug, timestamps, and a banner_image and card_image URL. No article body, so an index page stays fast.
One post
GET /blog-articles/{slug} takes the slug or the numeric id. Alongside everything in the list, it adds the body and the SEO fields.
| Field | Notes |
|---|---|
article | The article body. |
html | The rendered HTML. This is what you put on the page. |
caption | The banner caption, if there is one. |
meta_title, meta_description | For your page head. |
meta_canonical | The canonical URL, where one is set. |
no_index | When true, keep this post out of search engines. |
Scoping
An organisation key sees every published post and can filter to one tribe with tribe_slug. A tribe key sees only posts attached to that tribe — which is what makes a per-tribe blog work without any filtering on your side.
Caching
Both endpoints are cached and send an ETag, so a busy blog index costs very little. A newly published post can take a few minutes to appear — longer if your own site caches on top. Plan for that when someone asks why their post is not live yet.
card_image for the tiles. Call the single-post endpoint only when a visitor opens a post, and render html directly. Two calls, both cached.