Filtering Operators

List endpoints support a structured filter syntax that lets you query records by any filterable field using a range of comparison and matching operators.

Filter Syntax

Filters are passed as indexed query parameters:

filters[N][field]=<field>
filters[N][op]=<operator>
filters[N][value]=<value>

Where N is a zero-based index. Multiple filters can be combined and all must match (logical AND).

Example — Single Filter

Calls with AI score above 80:

curl "https://api.meetrox.ai/v1/calls?filters[0][field]=ai_score&filters[0][op]=>&filters[0][value]=80" \
  -H "x-api-key: YOUR_API_KEY"

Example — Multiple Filters

Calls longer than 10 minutes with a prospect from Acme:

curl "https://api.meetrox.ai/v1/calls\
?filters[0][field]=duration&filters[0][op]=>&filters[0][value]=600\
&filters[1][field]=lead_company&filters[1][op]==~&filters[1][value]=acme" \
  -H "x-api-key: YOUR_API_KEY"

Operators

Equality

Operator	Description	Example value
`==`	Exact match	`"video"`, `82`, `true`
`!=`	Not equal	`"audio"`

Comparisons

Applicable to numeric and datetime fields (ai_score, duration, timestamp, inserted_at, updated_at, rep_talk_ratio, etc.).

Operator	Description
`>`	Greater than
`>=`	Greater than or equal
`<`	Less than
`<=`	Less than or equal

Null / Presence

These operators do not require a value parameter.

Operator	Description
`empty`	Field is `null` or empty
`not_empty`	Field is not `null` and not empty

List Membership

The value must be a comma-separated list.

Operator	Description	Example value
`in`	Field value is in the list	`"audio,video"`
`not_in`	Field value is not in the list	`"chat,file"`

String Matching

Applicable to text fields (title, lead_name, lead_company).

Operator	Description	Notes
`=~`	Regex match	Uses database-level regex
`like`	SQL `LIKE` pattern	Case-sensitive, use `%` as wildcard
`not_like`	SQL `NOT LIKE` pattern	Case-sensitive
`ilike`	SQL `ILIKE` pattern	Case-insensitive, use `%` as wildcard
`not_ilike`	SQL `NOT ILIKE` pattern	Case-insensitive
`like_and`	Space-separated terms, all must match	Case-sensitive
`like_or`	Space-separated terms, any must match	Case-sensitive
`ilike_and`	Space-separated terms, all must match	Case-insensitive
`ilike_or`	Space-separated terms, any must match	Case-insensitive

Practical Examples

Calls from a date range

# All calls in May 2026
filters[0][field]=timestamp&filters[0][op]=>=&filters[0][value]=2026-05-01T00:00:00Z
filters[1][field]=timestamp&filters[1][op]=<&filters[1][value]=2026-06-01T00:00:00Z

Calls by format

# Only video calls
filters[0][field]=type&filters[0][op]===%20&filters[0][value]=video

Calls with missing AI score

filters[0][field]=ai_score&filters[0][op]=empty

Calls with a specific lead company (case-insensitive partial match)

filters[0][field]=lead_company&filters[0][op]=ilike&filters[0][value]=%acme%

Calls in a specific score range

filters[0][field]=ai_score&filters[0][op]=>=&filters[0][value]=70
filters[1][field]=ai_score&filters[1][op]=<=&filters[1][value]=90

Notes

All filters are combined with logical AND. There is no OR across filters.
Date/datetime values must follow ISO 8601 format (e.g., 2026-05-20T14:00:00Z).
For empty and not_empty, the value parameter can be omitted entirely.
For in and not_in, pass comma-separated values in a single value string (e.g., audio,video).
See Calls for the full list of filterable fields available on that endpoint.