Filters are passed as an object toDocumentation Index
Fetch the complete documentation index at: https://docs.usehasp.com/llms.txt
Use this file to discover all available pages before exploring further.
listRecords and paginateRecords. Multiple fields use AND logic — all conditions must match.
Syntax
Operators
| Operator | Description | Example |
|---|---|---|
eq | Equal | { status: { eq: 'open' } } |
neq | Not equal | { status: { neq: 'done' } } |
in | In array | { status: { in: ['open', 'in_progress'] } } |
contains | String contains (case-insensitive) | { title: { contains: 'milk' } } |
gt | Greater than | { priority: { gt: 3 } } |
gte | Greater than or equal | { due_date: { gte: '2026-03-01' } } |
lt | Less than | { priority: { lt: 5 } } |
lte | Less than or equal | { due_date: { lte: '2026-03-31' } } |
Filtering on a field key that does not exist in the entity schema returns an empty result set — no error is thrown.
Examples
multi_select Fields
Usecontains to filter records where a multi-select field includes a specific value:
No Client-Side Filtering
Always use the filter DSL instead of fetching all records and filtering in JavaScript. Filtering server-side is dramatically more efficient and doesn’t break pagination.OR Logic
OR logic across fields is not currently supported — all conditions use AND. If you need OR behaviour (e.g. “status is open OR assignee is me”), make two separate requests and merge the results in your app. Deduplicate byid before rendering to handle any records that appear in both result sets.