Get Many Activities
Retrieves the history of all campaign activities and steps performed (optionally filtered by activity type and campaign).
Filtering by date
Activities can be filtered on theircreatedAt field using either of two
naming conventions:
minDate/maxDate(primary)startDate/endDate(aliases, kept consistent with sibling endpoints such as/campaigns/{campaignId}/stats)
1715385600) or
an ISO 8601 datetime (e.g. 2026-05-11T00:00:00Z).
When both names are provided, the primary one wins: minDate takes
precedence over startDate, and maxDate over endDate. maxDate must
be strictly greater than minDate when both are set.
Response
The response can includesequenceStep and totalSequenceStep fields, which are zero-indexed (starting at 0).
Activities also carry stepId, the stable identifier of the step that produced
them. Unlike sequenceStep — a position that shifts when a sequence’s steps are
reordered — stepId always points at the same step, so prefer it when you store
a reference. sequenceStep keeps being returned exactly as before.
stepId is present on every activity created from now on. Activities recorded
earlier gain it progressively as historical records are backfilled, so treat it
as optional when you read back through history.Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Query Parameters
API version. v2 is mandatory
v2 Filter by activity type (e.g., paused)
Filter by campaign ID
Filter for first activity
Number of records to skip. Note: This is not traditional cursor-based pagination. To retrieve all activities, increment offset by the limit value on each request (e.g., offset=0, then offset=100, then offset=200, etc.).
Number of activities to retrieve. Default: 100. Maximum: 100
Filter by lead ID
Filter activities by createdAt >= minDate. Accepts either a Unix timestamp in seconds (e.g. 1715385600) or an ISO 8601 datetime (e.g. 2026-05-11T00:00:00Z). minDate is the primary name; startDate is accepted as an alias and minDate takes precedence when both are provided.
Filter activities by createdAt <= maxDate. Accepts either a Unix timestamp in seconds (e.g. 1715385600) or an ISO 8601 datetime (e.g. 2026-05-11T00:00:00Z). Must be strictly greater than minDate when both are provided. maxDate is the primary name; endDate is accepted as an alias and maxDate takes precedence when both are provided.
Alias for minDate, provided for consistency with sibling endpoints (e.g. /campaigns/{campaignId}/stats). Accepts either a Unix timestamp in seconds or an ISO 8601 datetime. Ignored when minDate is also provided.
Alias for maxDate, provided for consistency with sibling endpoints (e.g. /campaigns/{campaignId}/stats). Accepts either a Unix timestamp in seconds or an ISO 8601 datetime. Ignored when maxDate is also provided.
Response
Success
Unique activity identifier
Activity type (emailOpened, emailClicked, emailReplied, etc.)
Associated lead ID
Campaign ID
Sequence ID
Stable identifier of the sequence step that produced this activity. Present on every activity created from now on; older activities gain it progressively as historical records are backfilled, so treat it as optional when reading history.
0-based position of the step within the sequence. Still emitted on every activity, unchanged. Prefer stepId for a reference that survives steps being reordered.
0-based count of the sequence steps already delivered to this lead.
When the activity occurred