API
Our Team: a tribe's public team members on the API
GET /wordpress/tribes/{slug}/our-team returns the team members a tribe has chosen to show publicly, in the order they were arranged, with contact details they opted in to.
Last updated September 2, 2026
GET https://api.gorilladash.com/api/v1/wordpress/tribes/{slug}/our-team returns the people a tribe wants to show on its website — the "meet the team" section — drawn from the organisation chart in Gorilla Dash.
The {slug} in the path is the tribe slug. Takes results_per_page, which defaults to 10.
Who appears
Only people who are active and marked show on website, at a tribe that is active, testing or opening soon. They come back in the order you arranged them in the organisation chart, so head of office appears above the apprentice without any sorting on your side.
What comes back
| Field | Notes |
|---|---|
id, slug | Identity. Use the slug for a per-person page. |
first_name, last_name | Their name. |
position | Their job title. |
business_name | The business they are listed under. |
profile | Their biography. |
order | Their position in the chart. Already applied to the ordering. |
avatar | Their photo, or null. |
email | Only if they made their email public. Otherwise null. |
mobile | Only if they made their mobile public. Otherwise null. The value is E.164 — +61412345678 — so format it before you print it. |
telephone | Only if they made their phone public. Otherwise null. |
email, mobile or telephone means that person chose not to publish it — the value exists in Gorilla Dash and is deliberately withheld here. Never fill the gap from another endpoint. Render what you are given and leave the rest out.Building the page
- Render in the order returned. Do not re-sort alphabetically — the chart order is a deliberate choice.
- Handle a null
avatarwith a placeholder rather than a broken image. - Only show a contact link when the field is present.
- Pair this with
GET /wordpress/tribes/{id}, whoseintroduction_teamis the copy meant to sit above this section.
The endpoint is cached and sends an ETag, so a new starter can take a few minutes to appear on the site.