Authentication

Every request to a telecrm API must include a bearer token in the Authorization header. Tokens are generated in the telecrm dashboard and are scoped to a single API type — Async or Sync.

Generate a token

Log in to the telecrm dashboard.
Navigate to Settings → Website and API → API token.
Click Create new token.
Enter a descriptive token name.
Select the token type: Async or Sync.
Click Create, then Copy Token.
Download the token as a backup.

WARNING

The token is shown only once. If lost, it cannot be recovered — generate a new token and update any clients that used the old one.

TIP

A workspace is limited to 3 tokens of each type — up to 3 Async tokens and up to 3 Sync tokens.

Token type matters

Async and Sync tokens are not interchangeable.

An Async token is rejected by Sync endpoints.
A Sync token is rejected by Async endpoints.

The two APIs report the rejection differently:

API	Status	Body
Sync	`401`	`{ "error": { "code": "NOT_AUTHORIZED", "message": … } }`
Async	`403`	The plain-text string `NOT_AUTHORIZED`

Update availability is a third case — it returns 403 with the literal body false.

Use a token in a request

Pass the token as a bearer credential in the Authorization header.

Authorization: Bearer <token>
Content-Type: application/json

Example request

bash

curl -X POST "https://next-api.telecrm.in/enterprise/{enterpriseId}/autoupdatelead" \
  -H "Authorization: Bearer YOUR_ASYNC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "fields": {
      "name": "Jane Doe",
      "phone": "919999999999"
    }
  }'

Replace {enterpriseId} with your enterprise ID, also available in Settings → Website and API.

Revoking a token

To invalidate a token immediately, delete it in Settings → Website and API → API token. Requests using the deleted token start being rejected from the next call — 401 on Sync, 403 on Async.

Authentication ​

Generate a token ​

Token type matters ​

Use a token in a request ​