List contact engagements

Keyset cursor from a previous list response. Cursors encode the sort key and record id tie-breaker from the last row on the prior page — they are not offset tokens and do not isolate a point-in-time snapshot.

For order_by on updated_at, cursors use the pa_uac_1_ prefix and encode { "id", "updatedAt" }. For GET /v2/engagements with order_by on start_at, cursors use the pa_sac_1_ prefix and encode { "id", "startAt" }. A cursor is bound to the sort field, not the direction. An updated_at cursor cannot be used with order_by=start_at:* (or the reverse). Reusing a cursor with the opposite direction for the same field is accepted, but can skip or repeat records.

Live keyset pagination can re-deliver a row whose sort key moved forward during the walk (design sync jobs to upsert by id) and can skip a row whose sort key moved backward.

Comma-separated list of additional engagement fields to include in the response. Valid values: companies, contacts, owner, action_items, signals, transcript, transcript_timeline, media_url, tags. Requesting companies also requires companies:read. Requesting contacts also requires contacts:read. Requesting owner also requires users:read. transcript returns aggregated engagement text, which can include Markdown or HTML plus extracted attachment text; it is not structured speaker or timing data. transcript_timeline additionally requires transcript_timelines:read and returns the structured timeline object (or null when no primary timeline exists or when timeline serialization fails for that engagement). Engagement list requests that include transcript_timeline have an effective page limit of 25, even when a larger limit is supplied. For speaker-aware or time-aligned ingest, use expand=transcript_timeline or GET /v2/engagements/{engagement_id}/transcript_timeline instead.