Get Enquiries
Paginated list of the calling organisation’s (or tribe’s) enquiries.
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:00is honoured. - Child-aware: the embedded
personblock 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), notupdated_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.
A tribe API key passing a tribe_id for a different tribe gets 403 (it used to silently ignore the parameter).
Success is HTTP 201, not 200.
Headers
Query parameters
Records per page. 1-1000, default 100. Over 1000 returns 422.
