Search actions
Filters the lead's timeline by action type, performer, and creation time. Unlike create actions, this endpoint can search all action types — calls, messages, system events, and integrations — not just custom and payment actions.
Results sort newest-first by action creation timestamp.
Request
| Field | Value |
|---|---|
| Method | POST |
| URL | https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/{leadId}/action/search |
| Auth | Bearer token (Sync-typed). See Authentication. |
| Headers | Content-Type: application/json |
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
enterpriseId | string | yes | The enterprise (workspace) ID. |
leadId | string | yes | The lead's ID. |
Body
An empty body returns all actions on the lead. All filters are optional and combine with AND logic.
| Field | Type | Description |
|---|---|---|
type | string | Action type. Custom actions by their numeric code (e.g. "1001"); built-in types from the Action Types enum. |
created_on | object | Action creation time window: { from, to }. Each bound accepts Unix ms or a date-time string. |
performed_by | string or array | Team member ID(s) who performed the action. |
Example request
Find outgoing calls in April 2026:
bash
curl -X POST "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/603d2b2f9b1e8a001c8e4f5c/action/search" \
-H "Authorization: Bearer YOUR_SYNC_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"type": "OUTGOING_CALL",
"created_on": {
"from": "01/04/2026 00:00:00",
"to": "30/04/2026 23:59:59"
}
}'Responses
200 OK
Paginated action results, sorted newest-first.
json
{
"data": [
{
"type": "OUTGOING_CALL"
}
],
"total_count": 1,
"skip": 0,
"limit": 10
}400 Bad Request
Invalid filter values.
json
{
"error": {
"code": "BAD_REQUEST",
"message": "Invalid filter"
}
}401 Unauthorized
See the universal 401 in the overview.
404 Not Found
json
{
"error": {
"code": "LEAD_NOT_FOUND",
"message": "Lead with given ID was not found"
}
}Notes
- See Action Types for the complete
typeenum, organized by category (calls, messages, lifecycle, integrations, etc.). - Use
POST /lead/{leadId}/action/{actionId}to fetch the full body of a specific match — search results return only the type, not the full action body for non-writable types.