Get a custom field
Returns the full definition of a single custom field, looked up by its API name. The shape always matches detail=true from GET /custom-fields.
Request
| Field | Value |
|---|---|
| Method | GET |
| URL | https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/custom-fields/{apiName} |
| Auth | Bearer token (Sync-typed). See Authentication. |
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
enterpriseId | string | yes | The enterprise (workspace) ID. |
apiName | string | yes | API name of the field (e.g. contact_source, deal_size). Case-sensitive. |
Example request
bash
curl "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/custom-fields/contact_source" \
-H "Authorization: Bearer YOUR_SYNC_TOKEN"Responses
200 OK
json
{
"id": "5f8a1b2c3d4e5f6a7b8c9d0e",
"type": "DROPDOWN",
"apiName": "contact_source",
"description": "How the lead was sourced",
"lockAfterCreate": false,
"isLeadid": false,
"options": [
{ "id": "opt_1", "label": "Website" },
{ "id": "opt_2", "label": "Referral" },
{ "id": "opt_3", "label": "Cold Call" }
]
}401 Unauthorized
See the universal 401 in the overview.
404 Not Found
json
{
"error": {
"code": "NOT_FOUND",
"message": "Could not find custom field with apiName contact_source"
}
}Notes
- Find the API name in Settings → Lead Fields → click the field → Properties → API name, or by listing all fields via
GET /custom-fields. - API names are case-sensitive —
contact_sourceandContact_Sourceare different lookups.