Telegram Raw API

Access raw Telegram TL methods through REST endpoints. Each connected Telegram account can execute any of the 700+ available methods.

Rate limits

Rate limits are enforced by Telegram, not by CRMchat. When you exceed Telegram's limits, the API returns a FLOOD_WAIT_X error with the number of seconds to wait:

{
  "code": "BAD_REQUEST",
  "message": "FLOOD_WAIT_42",
  "data": {
    "code": "TELEGRAM_RPC_ERROR",
    "tlErrorCode": 420,
    "tlErrorMessage": "FLOOD_WAIT_42"
  }
}

Your application should parse the wait duration from the error message and retry after that period. Different methods have different limits — there are no published numbers, but generally:

• Messaging: ~30 messages per second to different chats, slower for the same chat
• Bulk reads (e.g., messages.getHistory): a few requests per second
• Resolve/search: stricter limits, cache results when possible
• Account-wide: Telegram tracks overall activity per account, not per API key

Endpoint

All methods are called via:

POST /v1/workspaces/{workspaceId}/telegram-accounts/{accountId}/call/{method}

Authentication

Use your API key as a Bearer token in the Authorization header.

Request format

{
  "params": {
    // Method-specific parameters
  }
}

Response format

{
  "result": {
    // TL object response
  }
}

Type conventions

Available schemas

Available schemas

OpenAPI specs are available at three granularity levels for AI agent consumption:

• Full spec: /v1/tl-spec/all.json — All methods (~700+)
• Per namespace: /v1/tl-spec/{namespace}.json — Methods grouped by namespace (e.g., messages, channels)
• Per method: /v1/tl-spec/{namespace}/{method}.json — Single method spec