Skip to main content
All list endpoints accept filters as query parameters. Filters are optional and combine with AND logic: every filter sent must be satisfied for a record to appear in the result. Invalid filters return 422 with the exact field that failed validation.

Filters by resource

GET /v1/people


GET /v1/companies


GET /v1/deals


GET /v1/pipelines

The pipelines list endpoint does not support field-level filters. Use order_by and order to control the sort order.

GET /v1/tasks


GET /v1/activities

entity and id are always required together. Requests without them return 422.

GET /v1/products


GET /v1/tags


GET /v1/lists


GET /v1/task-types


GET /v1/custom-fields


Combining filters with pagination

Filters combine normally with pagination parameters (page, per_page, order_by, order). The meta.total in the response always reflects the total number of records matching the applied filters, not the overall workspace total.

Validation errors

Filters with invalid values return 422 identifying the field: