Skip to main content
GET
List people
GET /v1/people returns the workspace’s people (contacts), page-paginated with page and limit (max 100). It does not accept inline filtering or sorting — those query params are ignored. To filter or sort people — including across related objects — use the records query: POST /v1/records/query with root: "people". It exposes the full filters / raw whereClause and orderBy model. For the operator set and pagination notes see Filtering & sorting. Filter and sort on a related (included) object by nesting into the relationship — the same relationships you pass to include.
  • To-one relations nest directly: { "issuer": { "name": { "_eq": "Acme" } } }, and sort by a dot-path: "orderBy": { "field": "issuer.name", "direction": "asc" }.
  • To-many relations must be quantified with _some, _every, or _none: { "items": { "_some": { "quantity": { "_gt": 1 } } } }. They are not directly sortable (a to-many sort needs an aggregate proxy).
  • Composite composite_* columns are virtual — filter and sort on their underlying source fields, not on the composite.
Workspace row-level security applies at every hop, so a related-object filter never widens your tenant scope. Full operator set, deep-nesting rules, and pagination notes: Filtering & sorting. This resource’s related objects (the ones you can include) and how to filter or sort on each: Replace field_name with any field of the related object. See its object-reference page for the full field list. Filter by a to-one relation (and sort by it):
Filter by a to-many relation (quantified — bare nesting is invalid):

Headers

Authorization
string
required

Bearer token for authentication

Query Parameters

page
integer
default:1

1-based page number.

Required range: x >= 1
limit
integer
default:20

People per page (max 100).

Required range: 1 <= x <= 100

Response

A page of people.

data
object[]
required
meta
object