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.

Query parameters

Pagination is via query string, not body.

Name	Type	Default	Description
skip	number	0	Number of results to skip.
limit	number	10	Page size. Must be between 1 and 100; otherwise returns 400.
onlyCount	boolean	false	When true, returns only the match count without action data.
hidePII	boolean	false	When true, personal data in the returned actions is redacted.

Body

An empty body returns all actions on the lead. All filters are optional and combine with AND logic.

Field	Type	Description
type	string or array	Action type(s). Custom actions by their numeric code (e.g. "1001" — server-prefixes to ACTION_1001); built-in types from the Action Types enum. Uppercased server-side.
created_on	object	Action creation time window: { from, to }. Each bound accepts Unix ms or a DD/MM/YYYY HH:mm:ss string. from > to returns 400.
performed_by	string or array	Team member ID(s) who performed the action.

Example request

Find outgoing calls in April 2026:

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. data contains the full action objects — fields vary by action type.

{
  "data": [
    {
      "type": "OUTGOING_CALL",
      "...": "..."
    }
  ],
  "total_count": 1,
  "skip": 0,
  "limit": 10
}

400 Bad Request

An inverted created_on window, or a limit outside 1-100.

{
  "error": {
    "code": "BAD_REQUEST",
    "message": "created_on from is greater than to"
  }
}

401 Unauthorized

See the universal 401 in the overview.

404 Not Found

{
  "error": {
    "code": "LEAD_NOT_FOUND",
    "message": "Lead with ID 62ab16e not found"
  }
}

Notes

• See Action Types for the complete type enum, organized by category (calls, messages, lifecycle, integrations, etc.).
• Search returns full action objects for all matching types. The get-by-id endpoint, however, only retrieves custom, PAYMENT, and ATTACHMENT actions — other types return 400.