Telegram Subscriber History and Channel Mentions

Use charts to examine how a channel's metrics change over time. Use mentions to find publications that refer to a channel.

Select a chart

Metric	Endpoint
Subscribers	/v1/charts/subscribers
Message reach	/v1/charts/reach
Engagement rate by views	/v1/charts/err
Views of an individual message	/v1/messages/views

curl --fail-with-body --get "https://api.tlmtr.io/v1/charts/subscribers" \
  -H "x-api-key: $TELEMETRIO_API_KEY" \
  --data-urlencode "internal_id=$CHANNEL_ID"

Chart points contain a date and value. Choose aggregation from the endpoint's supported values, and inspect its response schema before combining different metrics. Subscribers and percentages have different units; message-view responses have their own structure.

The accessible history depends on the key's plan or individual settings. Missing points do not establish zero activity. Do not fill gaps with zero unless that is an explicit choice in your analysis.

List mentions

curl --fail-with-body --get "https://api.tlmtr.io/v1/channel/mentions" \
  -H "x-api-key: $TELEMETRIO_API_KEY" \
  --data-urlencode "internal_id=$CHANNEL_ID" \
  --data-urlencode "short_info=true"

The response includes mentions, total, related chats and an optional cursor. Pass the cursor back with the same filters. from_date and to_date use Unix seconds; the accessible mention period is limited by the key's history depth.

Use the mentions reference for supported mention kinds. A mention records a reference; its existence alone does not establish a paid placement.

Account for requests

Charts and mentions are channel-specific calls. A Credits API key can incur a first-access channel charge in addition to the request fee. Several chart calls for the same channel do not introduce that channel again within the same key's billing period.