Telegram Account Proxy User Guide

The Telegram account proxy provides an independent, persistent MCP and REST interface for your personal Telegram account. Each instance serves only one account, and the login session is stored in the instance's independent persistent volume.

This is a personal account authorization service, not the Telegram Bot API. Only connect accounts that you personally own and have explicitly authorized; do not use it for spam messages, bulk cold sending, or bypassing Telegram restrictions.

¶ Login

1. Create a Telegram account proxy instance in the console.
2. Once the instance is ready, click "Generate Login QR Code."
3. Open Settings → Devices → Link Desktop Device in the Telegram client and scan the QR code.
4. If the account has two-step verification enabled, enter the Telegram two-step verification password in the console. The password is submitted directly to your tenant instance and will not be saved in the platform configuration.

After a successful login, the instance will reuse the persistent login state after a restart or upgrade. Logging out will revoke the Telegram session for that instance.

¶ MCP Access

The console will display the exclusive MCP address and Bearer access token:

{
  "mcpServers": {
    "telegram": {
      "url": "https://telegram-bot-xxxxxxxxxxxx.app.acedata.cloud/mcp",
      "headers": {
        "Authorization": "Bearer <PROXY_ACCESS_TOKEN>"
      }
    }
  }
}

Please protect the Bearer token as you would your account password. All login, REST, and MCP interfaces must carry this token, except for /health.

¶ REST Example

View the currently authorized account:

curl https://telegram-bot-xxxxxxxxxxxx.app.acedata.cloud/api/whoami \
  -H "Authorization: Bearer $PROXY_ACCESS_TOKEN"

List recent sessions:

curl "https://telegram-bot-xxxxxxxxxxxx.app.acedata.cloud/api/chats?limit=20" \
  -H "Authorization: Bearer $PROXY_ACCESS_TOKEN"

Send a message:

curl -X POST https://telegram-bot-xxxxxxxxxxxx.app.acedata.cloud/api/messages \
  -H "Authorization: Bearer $PROXY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"target":"me","text":"Hello from my Telegram proxy"}'

target can be a session ID, username, or exact session name. Production automation should control the sending frequency and perform explicit confirmation before sending to third parties.