Telegram message detail API

Get one message of a public Telegram channel by channel handle and message number, or by its link: text, time posted, views, images. One object a call; $0.0020 per call. Errors, timeouts and objects that do not exist are not charged.

GEThttps://api.dataxapi.com/v1/telegram/messages/get
Also known astelegram posttg messageIn Chinese: Telegram 单条消息 API
id is in the link: t.me/<id>. Or pass the whole link as url.
Price$0.0020/ call · Errors and timeouts are not charged
Returns1 objectone post object
When an upstream failsRetried for youon the same route, or a backup route; never charged

Try it

Change a value and the request on the right follows.
Run · $0.0020

Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 50 calls.

Used to call POST /v1/telegram/messages/detail? It is this address now. What changed for old endpoints

The first 3 rows of a response recorded 2026-10-12 19:04 UTC.
FieldValue
typevideo
published_at2021-01-11 21:57 UTC
metrics.views4,350,000
curl -G "https://api.dataxapi.com/v1/telegram/messages/get" \
  --data-urlencode "id=telegram/401" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
  "code": "ok",
  "request_id": "50bc16a4-063b-4746-a75d-e37373b5e3eb",
  "data": {
    "item": {
      "id": "fieldnotes_studio/1687",
      "url": "https://t.me/fieldnotes_studio/1687",
      "type": "video",
      "text": "My honest take on weekend hiking, a month in.",
      "published_at": "2021-01-11T21:57:12.000Z",
      "author": { "username": "northside_coffee", "name": "Leo Park" },
      "metrics": { "views": 4350000 },
      "images": [],
      "approximate": [
        { "field": "metrics.views", "kind": "approximate" }
      ]
    }
  },
  "warnings": [],
  "meta": {
    "capability": "telegram.messages.get",
    "result_status": "complete",
    "fetched_at": "2026-10-12T19:04:45.000Z",
    "cached": false,
    "replayed": false,
    "unavailable": {
      "title": "platform",
      "lang": "capability",
      "author.id": "capability",
      "author.avatar_url": "capability",
      "author.verified": "capability",
      "author.followers": "capability",
      "metrics.likes": "platform",
      "metrics.comments": "capability",
      "metrics.shares": "capability",
      "metrics.favorites": "platform",
      "metrics.reposts": "capability",
      "hashtags": "capability",
      "mentions": "capability",
      "is_pinned": "capability",
      "post_id": "capability",
      "parent_id": "capability",
      "root_id": "capability"
    },
    "billing": {
      "amount": "0.002",
      "currency": "USD",
      "balance_after": "9.998"
    }
  }
}

From a response recorded 2026-10-12 19:04 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.

Size as sent: 1.4 KB in the standard view (1.3 KB compact, 1.4 KB full).

This example as a JSON file

curl -G "https://api.dataxapi.com/v1/telegram/messages/get" \
  --data-urlencode "id=telegram/401" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI

dx = DataXAPI()  # reads DATAXAPI_API_KEY
result = dx.telegram.messages.get(id="telegram/401")
print(result["data"]["item"])
import { DataXAPI } from "@dataxapi/sdk";

const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.telegram.messages.get({ id: "telegram/401" });
console.log(result.data.item);
dataxapi call telegram.messages.get id=telegram/401
{
  "mcpServers": {
    "dataxapi": {
      "type": "http",
      "url": "https://api.dataxapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${DATAXAPI_API_KEY}"
      }
    }
  }
}

Add this to your MCP client, then ask your agent to call telegram.messages.get.

Parameters

idtextgive exactly one of id, url

The channel's handle and the message's number joined by a slash, as in telegram/401. Example: telegram/401.

urltextgive exactly one of id, url

Link to the message: t.me, then the channel, then the number. Example: https://t.me/telegram/401. Full link: https://t.me/telegram/401.

viewtext

How much of each item to return. All three cost the same. Values: compact, standard (default), full.

fieldslist of text

Return only these fields. Each by its path, such as author.name.

Known limits

Returned fields

data.item is one post object. Stable: fields are only ever added.

idtextcompact

ID; pass it unchanged to the get endpoint

On this platform: The channel's handle and the message's number, as in telegram/401; pass it unchanged to the message endpoint

urllinkcompact

Link that opens the post

typetextcompact

Content formatvideoimagetextarticle

titletextcompactThe platform has none

Title

texttextcompact

Body text

Long text: the compact view keeps the first 500 characters and says so in warnings.

langtextstandardNot provided here

Language of the text

Show all 35 fields →
published_attimecompact

When it was published

authorobjectcompact

Author

author.idtextcompactNot provided here

Author's account ID

author.usernametextcompact

Author's handle

On this platform: Handle of the channel the message is in

author.nametextcompact

Author's display name

author.avatar_urllinkstandardNot provided here

Author's avatar

author.verifiedyes/nostandardNot provided here

Whether the author is verified

author.followersintegerstandardNot provided here

Author's follower count

metricsobjectcompact

Engagement counts

metrics.likesintegercompactThe platform has none

Likes

metrics.commentsintegercompactNot provided here

Comments

metrics.sharesintegercompactNot provided here

Shares

metrics.favoritesintegercompactThe platform has none

Saves

metrics.viewsintegercompact

Views

On this platform: Views; from a thousand up the platform shows a rounded number

metrics.repostsintegercompactNot provided here

Reposts

imageslist of linkstandard

Image addresses

hashtagslist of textstandardNot provided here

Hashtags, without the #

mentionslist of objectstandardNot provided here

Accounts mentioned in the text

mentions[].idtextstandardNot provided here

Account ID

mentions[].usernametextstandardNot provided here

Handle

mentions[].nametextstandardNot provided here

Display name

is_pinnedyes/nostandardNot provided here

Whether the author pinned it

post_idtextcompactNot provided here

ID of the thread's root post when this is a reply; otherwise null

parent_idtextcompactNot provided here

ID of the item it replies to directly; otherwise null

root_idtextcompactNot provided here

ID of the first-level reply its thread hangs under

ext.numberintegerfull

The message's number within its channel; with the channel's handle it locates the message

approximatelist of objectcompact

Which numbers of this item are approximate or lower bounds; absent when all are exact

approximate[].fieldtextcompact

Path of the field, such as metrics.views

approximate[].kindtextcompact

Approximate, or a lower boundapproximatelower_bound

Typical size of one item: compact 598 B, standard 610 B, full 631 B (measured on the response recorded 2026-10-12 19:04 UTC).

What this endpoint cannot give

titleThe platform has none
langNot provided here
author.idNot provided here
author.avatar_urlNot provided here
author.verifiedNot provided here
author.followersNot provided here
metrics.likesThe platform has none
metrics.commentsNot provided here
metrics.sharesNot provided here
metrics.favoritesThe platform has none
metrics.repostsNot provided here
hashtagsNot provided here
mentionsNot provided here
mentions[].idNot provided here
mentions[].usernameNot provided here
mentions[].nameNot provided here
is_pinnedNot provided here
post_idNot provided here
parent_idNot provided here
root_idNot provided here

When you are charged

A result with data$0.0020, once per call
The object does not exist (404)not charged
Invalid parameters, a failure of ours or of the data source, a timeoutnot charged
CaseCharged
The most one call can cost$0.0020 (send X-Max-Price to refuse anything above your own limit)

Prices as read 2026-10-21 09:10 UTC, under price book 2, in effect since 2026-10-17 11:00 UTC; the Playground reads the price in force before a run.

If the object does not exist

The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted.

Errors

What this endpoint can answer with; codes all endpoints share are on the full list.

HTTPCodeMeaningCharged
400invalid_paramsA parameter is invalidRetry: After a fixNo
402insufficient_balanceThe balance is too lowRetry: After a fixNo
404not_foundThe object does not exist, is private or was deletedRetry: NoNo
502upstream_failedThe data source failedRetry: YesNo
504timeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNo

All error codes →

Questions

How much does the Telegram message detail API cost?

$0.0020 per call. The most one call can cost is $0.0020.

When am I not charged?

Errors, timeouts and objects that do not exist are not charged.

What happens if the object does not exist?

The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted.

The same thing on other platforms

All 3 Telegram endpoints

Telegram endpoints

Use it in your AI

Copy this prompt

Your API key is built in, so there is nothing to configure.

Read https://dataxapi.com/agents.md and set up DataXAPI in this agent. My API key is dx_…; use it for every DataXAPI call.
Sign in to copy it with your key

No account yet? Sign-up takes an email and no card, and a failed call is never charged.

then paste

Paste it into your agent

It reads the page the prompt points to and connects itself.

Your agent
Read https://dataxapi.com/agents.md and set up DataXAPI in this agent. My API key is dx_••••; use it for every DataXAPI call.
DataXAPI connected · 5 tools ready
now try it

Now ask something

Use one of these, or your own words.

Read https://dataxapi.com/apis/telegram/messages/get.md and help me use the DataXAPI endpoint telegram.messages.get (Telegram message detail).
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call telegram.messages.get.Other clients →
Ask with this pageSends the Markdown version
Brief for an AIEverything needed to call it, as text
Show the text
Use the DataXAPI endpoint telegram.messages.get (Telegram message detail). Get one message of a public Telegram channel by channel handle and message number, or by its link: text, time posted, views, images.
Call GET https://api.dataxapi.com/v1/telegram/messages/get with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code.
Parameters:
- id: The channel's handle and the message's number joined by a slash, as in telegram/401. Example: telegram/401.
- url: Link to the message: t.me, then the channel, then the number. Example: https://t.me/telegram/401. Full link: https://t.me/telegram/401.
- view: How much of each item to return. All three cost the same. Values: compact, standard (default), full.
- fields: Return only these fields. Each by its path, such as author.name.
Price: $0.0020 per call. Errors, timeouts and objects that do not exist are not charged.
The answer is JSON: data.item holds post; meta.billing.amount is what this call was charged.
Example:
curl -G "https://api.dataxapi.com/v1/telegram/messages/get" \
  --data-urlencode "id=telegram/401" \
  -H "Authorization: Bearer $DATAXAPI_API_KEY"
Full reference in Markdown: https://dataxapi.com/apis/telegram/messages/get.md

Names and identifiers

In Chinese
Telegram 单条消息 API
Endpoint ID
telegram.messages.get
Endpoint
GET /v1/telegram/messages/get
Last checked 2026-10-21 09:10 UTC.View the Markdown versionopenapi.jsonllms.txt

Start with one key.

207 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.

Start free