Get an action
Retrieves a single action by ID. Only custom actions, PAYMENT actions and ATTACHMENT actions can be retrieved through this endpoint — other types return 400.
For broader timeline queries (calls, messages, system events), use search actions.
Request
| Field | Value |
|---|---|
| Method | GET |
| URL | https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/{leadId}/action/{actionId} |
| Auth | Bearer token (Sync-typed). See Authentication. |
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
enterpriseId | string | yes | The enterprise (workspace) ID. |
leadId | string | yes | The lead's ID. |
actionId | string | yes | The action's ID. |
Query parameters
| Name | Type | Default | Description |
|---|---|---|---|
hidePII | boolean | false | When true, personal data in the action's fields is redacted. |
Example request
bash
curl "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/603d2b2f9b1e8a001c8e4f5c/action/603d2b2f9b1e8a001c8e4f5d" \
-H "Authorization: Bearer YOUR_SYNC_TOKEN"Responses
200 OK
The action is wrapped in an action key. Note that type comes back in the full ACTION_<code> form — the bare numeric code is a write-side format only.
Custom action:
json
{
"action": {
"type": "ACTION_1001",
"fields": {
"note": "Site visit completed"
},
"creationTimestamp": 1735689600000
}
}Payment action:
json
{
"action": {
"type": "PAYMENT",
"status": "COMPLETED",
"currency": "INR",
"amount": 5000
}
}Custom action fields are returned keyed by API name, with dropdown and tag IDs resolved to their labels.
400 Bad Request
The action exists but its type is not retrievable through the public API.
json
{
"error": {
"code": "BAD_REQUEST",
"message": "Only custom actions, payment actions and attachments can be retrieved"
}
}401 Unauthorized
See the universal 401 in the overview.
404 Not Found
json
{
"error": {
"code": "ACTION_NOT_FOUND",
"message": "Action with ID 62ab16e was not found."
}
}