Verify Telegram signal channel (bot membership)

curl --request POST \ --url https://mcp.echozero.app/api/v1/agents/{id}/telegram/verify \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "channel": "@MySignalsChannel" } '

{ "success": true, "data": { "verificationResult": "verified", "channelId": "<string>", "channelName": "<string>", "channelIconUrl": "<string>", "memberCount": 123, "message": "<string>" } }

Authorizations

Authorization

string

header

required

User JWT access token issued by POST /api/auth/verify or POST /api/auth/social/verify. Routes that accept both auth modes declare api-key and bearer-jwt security schemes.

Headers

x-signature

string

HMAC-SHA256 signature: HMAC-SHA256(secretKey, timestamp + METHOD + path + body). Required for API-key authenticated requests (JWT/OAuth session auth is exempt).

x-timestamp

string

Request timestamp in epoch milliseconds. Required with x-signature for API-key auth. Rejected if drift exceeds 5 minutes.

Path Parameters

string

required

Body

application/json

channel

string

required

Telegram public channel @username, t.me/slug, https://t.me/slug, or numeric chat id (-100…).

Required string length: 1 - 256

Example:

"@MySignalsChannel"

Response

Verification outcome; agent row updated unless channel could not be resolved.

success

boolean

required

Example:

true

data

object

required

Endpoint-specific payload

Show child attributes

Health

Auth

API Keys

User

Developer

Developer dashboard

Developer signal corpus

Trade Signals

Developer Agents (Marketplace)

Inbound Agent Signals

Trade

Token

Strategy

Agent

AI

Wallet

Notification

OAuth

Statics

Earn

Activity

Feed

Misc

Sandbox

MCP Protocol

Verify Telegram signal channel (bot membership)

Authorizations

Headers

Path Parameters

Body

Response