API
Customer reviews on the API
GET /reviews returns your featured public Google and Facebook reviews, shuffled, for a testimonials widget on a website.
Last updated September 2, 2026
GET https://api.gorilladash.com/api/v1/reviews returns the reviews you have chosen to feature. It is built for a testimonials strip on a website — not for review reporting, which lives in Gorilla Dash itself.
Parameters
| Parameter | Notes |
|---|---|
tribe_slug | Reviews featured on one tribe. Without it you get the organisation's featured reviews. |
rating | Minimum star rating. Defaults to 5. |
results_per_page | How many. Defaults to 5. |
page | Page number, from 1. |
THE DEFAULT IS FIVE STARS ONLY
Call this endpoint with no parameters and you get five-star reviews. If your widget looks empty, pass
rating=4 and see whether the reviews appear. This is the most common reason a testimonials block renders blank.What is included
Three conditions, all of which must hold:
- The review came from Google or Facebook. Reviews from other sources are not returned.
- It is a public review, not a private one.
- It is featured — featured for the organisation, or featured for the tribe when you pass
tribe_slug.
Those two featured flags are separate. A review featured for the organisation does not appear under a tribe, and the reverse. If a tribe's widget is empty, someone needs to feature reviews on that tribe.
What comes back
| Field | Notes |
|---|---|
id, organisation_id | Key your own records on id — nothing else in the payload is unique. |
social_author_name | Who left the review. |
social_message | What they wrote. |
rating | Stars out of five. |
review_source | Google or Facebook. |
social_datetime | When it was left. |
tribe_id, tribe_slug | The tribe it belongs to. |
The order is random on purpose
SHUFFLED, THEN HELD
Reviews come back in random order so a widget does not show the same three testimonials forever. The shuffle is then frozen for the cache window, so the same set is served for a while before it changes — which also means a page refresh will not always reshuffle. Both are intentional.
Because the order is random, paging through this endpoint is not meaningful. Ask for the number you want to display in one call.