Skip to navigation

Get Enquiries

View as Markdown

Paginated list of the calling organisation’s (or tribe’s) enquiries.

Filters

ParameterWhat it does
pagePage number, from 1.
results_per_page1–1000, default 100. Over 1000 returns 422.
tribe_idOnly one tribe’s enquiries. Organisation keys only; a tribe key naming a different tribe gets 403.
person_idOnly one contact’s enquiries.
created_afterCreated at or after this moment. Full ISO-8601 timestamp with its offset, compared to the second.
created_beforeCreated strictly before this moment. Must be later than created_after, or the request returns 422.
created_date_fromOlder, whole-day filter in UTC: created on or after this date (YYYY-MM-DD).
created_date_toOlder, whole-day filter in UTC: created on or before this date (YYYY-MM-DD).
updated_afterChanged since this timestamp. The one to use for syncing; see below.
include_personSend false to leave out the contact’s name, email, phone and address. person then comes back as null.
include_fieldsSend false to leave out the custom field answers, which often hold the same details. fields then comes back as null.

Reporting on one month — set created_after to the first moment of the month and created_before to the first moment of the next one, both in your own time zone. A lead created exactly at midnight belongs to the new month only, so back-to-back months never count a lead twice. URL-encode the offset’s + as %2B: a + left as it is arrives as a space and the request is refused with 422. For September in Sydney:

created_after=2026-09-01T00:00:00%2B10:00&created_before=2026-10-01T00:00:00%2B10:00

Counts and attribution only — add include_person=false&include_fields=false. The source, tribe, form and tracking parameters still come back, with no contact details.

Ordering — ascending id, the same walk as GET /people. (It is deliberately not newest-first: the filter is timestamp-based while the order is id-based, so newest-first would push the oldest changed enquiries onto later pages and a poller that advanced its cursor after page one would never see them again.)

Every payload carries organisation_id, tribe_id, tribe_slug, and a tribe block that now includes slug alongside id and name.

Incremental sync (updated_after)

  • Timestamp-granular and strictly greater-than (>). Send a full ISO-8601 timestamp; an offset such as +10:00 is honoured.
  • Child-aware: the embedded person block participates, so an enquiry resurfaces when its contact’s details change. Field, tracking and source edits already bump the enquiry itself.
  • Cursor on record_updated_at (the latest of the enquiry row and its person), not updated_at.
  • Cursor on the wall-clock time the poll started, not on max(record_updated_at) in the result.
  • Note: the enquiry-to-tribe link is deliberately excluded from the child legs (that pivot has no timestamps and is only written at creation).

Limits — results_per_page is 1–1000 (default 100); over 1000 returns HTTP 422. Rate limit is 120 req/min per API key per IP, under a 300 req/min per-IP ceiling.

API key permissions — a key limited to chosen endpoints needs Inquiries › GET /api/v1/enquiries ticked. Full Access keys, and keys made before endpoint permissions existed, already have it.

Success is HTTP 201, not 200.

Full guide: Reading enquiries out of Gorilla Dash.

Headers

GorillaDash-Api-KeystringOptional
Gorilla Dash API Key
GorillaDash-Api-SecretstringOptional
Gorilla Dash API Secret
X-Requested-WithstringOptional

Query parameters

results_per_pageintegerOptional

Records per page. 1-1000, default 100. Over 1000 returns 422.

Response headers

cache-controlstringOptional
x-ratelimit-limitstringOptional
x-ratelimit-remainingstringOptional

Response

Created
statusinteger
successboolean
datalist of objects
paginationobject