Filters

Filters are supported on every POST .../search endpoint:

POST /v2/accounts/search
POST /v2/contacts/search
POST /v2/opportunities/search

The /v1 compatibility routes support the same filters.

Filter shape

Each filter is an object with field, operator, and value.

{
  "filters": [
    { "field": "customer_tier", "operator": "eq", "value": "enterprise" },
    { "field": "amount", "operator": "gte", "value": 50000 }
  ]
}

Multiple filters in the array combine with AND. For date and timestamp fields, pass an ISO 8601 date or date-time string. Unix timestamps are not accepted in search filters.

Supported operators

Operator	Use
`eq`	Equal
`neq`	Not equal
`contains`	String contains substring
`not_contains`	String does not contain substring
`starts_with`	String starts with
`ends_with`	String ends with
`in`	Value is in array
`not_in`	Value is not in array
`gt`	Greater than
`gte`	Greater than or equal
`lt`	Less than
`lte`	Less than or equal
`between`	Between two values (inclusive). Pass `value` as `[min, max]`
`empty`	Field has no value
`not_empty`	Field has any value
`contains_all`	Array field contains all of the given values
`contains_none`	Array field contains none of the given values

For select, multi-select, and team-member fields, values can match an option’s value or label. The option object returned by the read API is also accepted. eq and in match any supplied value, while contains and contains_all require every supplied value.

Operator aliases

These read more naturally and resolve to the same operator under the hood.

Alias	Resolves to
`is`	`eq`
`is_not`	`neq`
`contain`	`contains`
`not_contain`	`not_contains`
`is_any_of`	`in`
`greater_than`	`gt`
`less_than`	`lt`
`before`	`lt`
`after`	`gt`
`include_all`	`contains_all`
`exclude_all`	`contains_none`

Custom field filters

Custom fields are filtered by their slug (the same key returned in custom_fields).

{
  "filters": [
    { "field": "customer_tier", "operator": "eq", "value": "enterprise" }
  ]
}

Look up slugs in the custom_field_definitions block of any response.

Examples

Range filter

{ "field": "amount", "operator": "between", "value": [10000, 50000] }

Array membership

{ "field": "industry", "operator": "in", "value": ["Software", "Fintech"] }

Date after

{ "field": "close_date", "operator": "after", "value": "2026-06-01" }

Empty check

{ "field": "next_action_date", "operator": "empty" }

Getting started

Accounts

Contacts

Opportunities

Notes & activities

Pipelines

Record operations

Record history

Filter shape

Supported operators

Operator aliases

Custom field filters

Examples

Range filter

Array membership

Date after

Empty check

​Filter shape

​Supported operators

​Operator aliases

​Custom field filters

​Examples

​Range filter

​Array membership

​Date after

​Empty check

Filter shape

Supported operators

Operator aliases

Custom field filters

Examples

Range filter

Array membership

Date after

Empty check