Filters and Orderings

Filter

You can apply filters to all post list requests. The filterable parameters vary depending on the endpoint and are explained in the documentation.

Filter Params

Every filter item require these 3 parameters (exempt NULL):

Param NameParam TypeDescription
fieldstringName of the field.
typestringType of filter as described below.
valuestringValue to filter against. It's always string.

Filter Types

TypeDescriptionExample
EQEqual{
"field": "status",
"type": "EQ",
"value": "CLOSED"
}
NEQNot Equal{
"field": "status",
"type": "NEQ",
"value": "CLOSED"
}
LTLess Than, can be used to filter integer, dates, datetimes.{
"field": "createdAt",
"type": "LT",
"value": "2023-01-01"
}
GTGreater Than, can be used to filter integer, dates, datetimes.{
"field": "createdAt",
"type": "GT",
"value": "2023-01-01"
}
LIKEYou can add wildcards sign % before/after or between string you searching for.{
"field": "displayName",
"type": "LIKE",
"value": "John%"
}
INIn{
"field": "status",
"type": "IN",
"value": "OPEN, CLOSED"
}
NOT_INNot In{
"field": "status",
"type": "NOT_IN",
"value": "OPEN, CLOSED"
}
IS_NULLFor this filter value param is not required.{
"field": "phoneNumber",
"type": "IS_NULL"
}
IS_NOT_NULLFor this filter value param is not required.{
"field": "phoneNumber",
"type": "IS_NOT_NULL"
}
MEMBER_OFMember Of
NOT_MEMBER_OFNot Member Of

Ordering

You can order all list requests by orderable fields.

{
    "limit": 5,
    "offset": 0,
    "filter": [],
    "order": [
        {
          "field": "points",
          "order":"DESC"
        }
    ]
}