Introduction
telecrm exposes two public APIs for programmatic access to a workspace:
- The Async API ingests leads at high volume. Requests are accepted and processed in the background.
- The Sync API reads, searches, and updates leads, actions, team members, and workspace metadata. Each request returns the operation's outcome immediately.
Both APIs operate on the same workspace data and use the same authentication mechanism, but they are designed for different workloads.
When to use which API
| Requirement | Use |
|---|---|
| Ingest leads from a website form, ad platform, webhook | Async |
| High throughput (thousands of requests per minute) | Async |
| Lowest cost per request | Async |
| Need the created lead's ID in the response | Sync |
| Need confirmation that a lead was created or updated | Sync |
| Read, search, or update an existing lead | Sync |
| Read workspace metadata (custom fields, actions, etc.) | Sync |
The Async API is lead-only — it cannot read, search, update arbitrary entities, or access metadata. For anything beyond fire-and-forget lead ingestion, use the Sync API.
Endpoint summary
| API | Base URL | Endpoints |
|---|---|---|
| Async | https://next-api.telecrm.in | POST /enterprise/{enterpriseId}/autoupdatelead |
| Sync | https://next.telecrm.in/autoupdate/v2 | Leads, actions, team members, enterprise metadata. 17 endpoints across 4 resource groups. |
Next steps
- Generate an API token in Authentication.
- Review the Concepts section — lead identifier, field types, and actions are shared across both APIs.
- Jump to the Async API overview to start ingesting leads, or the Sync API overview to read, search, and update workspace data.