Pagination and Filters

List endpoints use request-body cursor pagination. Send cursor.limit on the first request, then pass the returned cursor.next as cursor.after to fetch the next page.

POST /v1/signals/leads

Request

{
  "cursor": {
    "limit": 100
  }
}

{
  "data": [],
  "cursor": {
    "next": "opaque_cursor_from_the_response",
    "has_more": true
  }
}

Use the next cursor in a follow-up request:

Request

{
  "cursor": {
    "limit": 100,
    "after": "opaque_cursor_from_the_response"
  }
}

Common body fields

Field	Description
`cursor.limit`	Number of records to return. Maximum value is `100`.
`cursor.after`	Opaque cursor returned by the previous response. Omit it for the first page.

Keep the same filters and sort on every page. Cursors are tied to the requested sort and are rejected if reused with another sort.

Endpoint-specific time ranges

Endpoint	Start	End
`POST /v1/signals/leads`	`date_found.start_time` or `latest_signal.start_time`	Matching `end_time` field
`POST /v1/signals/accounts`	`date_found.start_time` or `latest_signal.start_time`	Matching `end_time` field
`POST /v1/monitor/leads`	`latest_activity.start_time`	`latest_activity.end_time`
`POST /v1/monitor/accounts`	`latest_activity.start_time`	`latest_activity.end_time`
`POST /v1/monitor/signals`	`observed_at.start_time`	`observed_at.end_time`

For Leads, the latest_signal range is applied to the same occurrence that matches signals and sheet_ids, so the returned signal.observed_at is always inside the requested window. Use filters on the Leads endpoint instead of nested result endpoints.

POST /v1/signals/leads

{
  "signals": ["topic_engagement_signal"],
  "sheet_ids": ["sh_6P9vR3"],
  "company_ids": ["co_4F7xN2"],
  "cursor": { "limit": 100 }
}

Get Started

API Basics

Signals

Monitor

Pagination and Filters

Common body fields

Endpoint-specific time ranges

​Common body fields

​Endpoint-specific time ranges

Common body fields

Endpoint-specific time ranges