Skip to main content
API endpoints that allow you to list typically provide two ways of filtering the results.

Query

You can use the query parameter to filter the results by a search term. The search term is matched against the name of the resource. For example, to list all the projects that contain the word “test” in their name, you can use the following query:
GET /api/projects?query=test

Filter

Filters allow for more precise queries on specific fields. The platform uses a SpringFilter-style DSL in the filter query parameter. For example, to list all projects named test:
GET /api/projects?filter=name=='test'

Fields

Field names are used directly. Dotted paths traverse related objects or structured fields. For example: category.updatedAt, project.organization.id, features.slug

Inputs

Numbers and booleans are unquoted. Strings, enums, UUIDs, and dates should be single-quoted. For example: status=='ACTIVE'

Operators

SyntaxDescriptionExample
and or ;Both expressions must matchstatus=='ACTIVE' and createdAt>'2026-01-01'
or or ,Either expression may matchstatus=='FAILED' or status=='PENDING'
( )Group expressions(status=='FAILED' or status=='PENDING') and project.id=='abc123'
Use parentheses when you want to override the default precedence of and before or.

Comparators

SyntaxDescriptionExample
==Equalsid==5
!=Not equalstatus!='ARCHIVED'
>Greater thancreatedAt>'2026-01-01'
>=Greater than or equalpriority>=5
<Less thanpageCount<100
<=Less than or equalpageCount<=100
=like=Wildcard string matchpath=like='*invoice*'
=in=Value is in a liststatus=in=('FAILED','PENDING')
is nullField is nullcompletedAt is null
is not nullField is not nullproject.id is not null
Use * as the wildcard character with =like=. For example, name=like='*invoice*'.

Common Examples

# Failed executions for a specific assistant
GET /api/executions?filter=status=='FAILED' and assistantId=='abc123'
# Document families whose path contains "invoice"
GET /api/document-families?filter=path=like='*invoice*'
# Pending document families
GET /api/document-families?filter=pendingProcessing==true
# Document families linked to a specific knowledge feature
GET /api/document-families?filter=features.id=='550e8400-e29b-41d4-a716-446655440000'

Sort

The sort query parameter uses semicolon-separated field:direction pairs:
GET /api/executions?sort=createdOn:desc
GET /api/projects?sort=name:asc;createdOn:desc
The direction defaults to asc. If you omit sort, the platform falls back to its resource-specific default order.