Documentation Index
Fetch the complete documentation index at: https://qomon-86428773.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
How queries are structured
Every search query is a two-level tree. The outer group sets the top-level logic; each inner group contains the individual conditions.Operators
| Operator | Meaning |
|---|---|
eql | Equals (tokenised match) |
not_eql | Does not equal |
eql:strictdata | Exact literal match |
not_eql:strictdata | Not an exact literal match |
ext | Has a value / is filled in |
not_ext | Has no value / is empty |
contains | Contains the substring |
not_contains | Does not contain the substring |
start_with | Starts with |
not_start_with | Does not start with |
gte | Greater than or equal |
lte | Less than or equal |
range | Between two values — use from and to |
"now", "now-30d", "now-1y", "now+1y". All dates are interpreted as UTC.
Getting a count without results
UsePOST /kpi with the same query body (omit per_page) to get the number of matching contacts instantly without fetching the full contact list.
{ "data": { "total": 1042 }, "status": "success" }
Custom fields and form answers
Custom fields and form answers use a different condition shape — you must supplyform_id and form_ref_ids alongside attr and ope:
form_id and form_ref_ids from GET /forms/custom_fields.