Pagination and synchronization

GET /calls and GET /prospects use page-number pagination.

Response metadata:

{
  "total": 151,
  "page": 1,
  "pageSize": 50,
  "hasMore": true
}

Calls and prospects are newest first. New records arriving during paging can shift offsets and cause duplicates or skipped records.

For reliable synchronization:

• Deduplicate calls and prospects by Sonik id.
• Continue while hasMore is true.
• Run periodic full reconciliation for important integrations.
• Coordinate workers so combined requests remain inside workspace rate limits.

Cursor or incremental pagination is separate roadmap work with no promised delivery date.

GET /prospect-activities is not paginated. It returns all matching activities newest first and can become large for long-lived prospects.