Get enterprise metadata
Returns workspace-level info: name, ID, creation timestamp, team size, industry, website, the lead identifier field ID, and active integrations.
Request
| Field | Value |
|---|---|
| Method | GET |
| URL | https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/metadata |
| Auth | Bearer token (Sync-typed). See Authentication. |
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
enterpriseId | string | yes | The enterprise (workspace) ID. |
Example request
bash
curl "https://next.telecrm.in/autoupdate/v2/enterprise/{enterpriseId}/metadata" \
-H "Authorization: Bearer YOUR_SYNC_TOKEN"Responses
200 OK
json
{
"name": "Acme Corporation",
"id": "ent_123456",
"creationTimeStamp": 1609459200000,
"teamSize": "50-100",
"industry": "Technology",
"website": "https://acme.com",
"leadIdentifierFieldId": "phone",
"integrations": ["WHATSAPP", "EMAIL", "SMS"]
}leadIdentifierFieldId is the internal ID of the field used as the workspace's lead identifier. It is not an API name, and it cannot be used as a payload key.
TIP
Don't try to resolve it yourself — GET /custom-fields does not return field IDs. It already marks the identifier for you: the entry with isLeadid: true carries the apiName every lead payload must include.
401 Unauthorized
See the universal 401 in the overview.
An enterprise ID that doesn't exist fails token verification, so it surfaces here as a 401 rather than a 404.