Update a lead

Updates fields on an existing lead. Only the fields supplied in the request body are changed; omitted fields are left unchanged.

Request

Field	Value
Method	POST
URL	https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/{leadId}
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

Field	Type	Required	Description
fields	object	yes	Fields to update, keyed by API name. Each value must conform to its field type.

WARNING

The lead's identifier field (default: phone) cannot be modified through this endpoint. Including it returns 403 INVALID_LEAD.

Example request

curl -X POST "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/lead/603d2b2f9b1e8a001c8e4f5c" \
  -H "Authorization: Bearer YOUR_SYNC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "fields": {
      "status": "Qualified",
      "rating": 4
    }
  }'

Responses

200 OK

Returns the lead's current state (fields only — actions are not included).

{
  "fields": {
    "name": "Jane Doe",
    "phone": "919999999999",
    "status": "Qualified",
    "rating": 4
  }
}

401 Unauthorized

See the universal 401 in the overview.

403 Forbidden

Attempted to modify the lead identifier.

{
  "error": {
    "code": "INVALID_LEAD",
    "message": "Cannot modify lead identifier field"
  }
}

404 Not Found

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

Notes

• To change a lead's status, set fields.status to a valid label from the workspace's lead stage pipeline. Unknown labels are dropped.
• Field values are validated against their defined type; invalid values produce a 400.
• Adding actions to an existing lead is a separate call — see POST /lead/{leadId}/action.