API
Reading your contacts: the people endpoint
GET /people returns your contact records with lookup by email, mobile or id, and incremental syncing with updated_after.
Last updated September 2, 2026
GET https://api.gorilladash.com/api/v1/people returns your contacts — everyone who has enquired, been imported, or been added in Gorilla Dash. Use it to look one person up, or to mirror the whole contact list into another system.
It is read-only. Contacts are created by pushing an enquiry, by importing, or in Gorilla Dash itself.
Filters
| Parameter | What it does |
|---|---|
page | Page number, from 1. |
results_per_page | Up to 1000. Defaults to 100. |
id | One contact by its Gorilla Dash id. |
email | Exact match on the email address. |
mobile | Exact match on the stored international number, such as +61412345678. |
tribe_id | Only contacts linked to one tribe. A tribe key may pass its own id, but naming any other tribe is refused with 403. |
created_date_from | Contacts created on or after this date. |
created_date_to | Contacts created on or before this date. |
updated_after | Contacts changed since this timestamp. |
email filter matches the stored address character for character, and mobile matches the stored international form. Searching for 0412 345 678 finds nothing — search for +61412345678. Normalise before you query.What comes back
| Field | Notes |
|---|---|
id | The contact id. Use it with person_id on the enquiries endpoint. |
organisation_id | Owning organisation. |
tribe_id, tribe_slug | The one tribe this contact belongs to. |
created_at, updated_at | When the contact was created, and when their own row last changed. |
record_updated_at | The later of the contact row and their tribe link. Cursor on this. |
first_name, last_name, email | Identity, and part of how incoming leads are matched. |
number_e164 | The phone number in international form. Use this one for anything automated. |
number_display | The same number formatted for reading. |
business_name | Their company, where known. |
initial_lead_source | How this contact first found you. |
initial_lead_campaign | The campaign behind that first contact. |
address_1, address_2, locality, state, postal_code, country | Their address, where known. |
Scoping
An organisation key sees every contact in the organisation and can narrow with tribe_id. A tribe key sees only contacts linked to that tribe, and asking it for a different tribe_id is refused with a 403.
Syncing contacts
Results come back oldest id first, and a contact counts as changed when their own details change or when their tribe link changes. Follow the pattern in the guide on keeping your system in sync: cursor on the wall-clock time your poll started, never on the newest timestamp in the results.
For the first full load, leave updated_after off and page through with results_per_page=1000.
This endpoint is not cached, so a contact created a moment ago is immediately readable.