DataNavoAPI / APIS / TELEGRAM

Telegram message detail

Telegram message detail: inspect inputs, post fields, pagination and limits, then run a local simulated request.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

What this capability does

Telegram message detail uses /v1/telegram/messages/get; GET returns data.item with post objects.

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

  • Capability: telegram.messages.get
  • Pagination: no cursor pagination; do not repeatedly request another page.
02

Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

  • GET: supply exactly one of id / url.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringOptional / conditionalThe channel's handle and the message's number joined by a slash, as in telegram/401—"telegram/401"
GETurlstringOptional / conditionalLink to the message: t.me, then the channel, then the number——
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
03

Try it locally

Use demo to inspect the fields, then explicitly select simulated with a customer test key to exercise settlement. Never put a customer key in a URL.

json
{
  "capability": "telegram.messages.get",
  "method": "GET",
  "params": {
    "id": "telegram/401"
  }
}
04

Output fields and interpretation

The post object permits missing or null values; do not replace missing measurements with zero. This table shows the main structure; the object reference covers nested fields.

FieldTypeMeaningSource scope
idstring | nullID; pass it unchanged to the get endpointTelegram
urlstring | nullLink that opens the postTelegram
typestring | nullContent formatTelegram
titlestring | nullTitleTelegram
textstring | nullBody textTelegram
langstring | nullLanguage of the text (standard view and up)Telegram
published_atstring | nullWhen it was publishedTelegram
authorobject | nullAuthorTelegram
author.idstring | nullAuthor's account IDTelegram
author.usernamestring | nullAuthor's handleTelegram
author.namestring | nullAuthor's display nameTelegram
author.avatar_urlstring | nullAuthor's avatar (standard view and up)Telegram
author.verifiedboolean | nullWhether the author is verified (standard view and up)Telegram
author.followersinteger | nullAuthor's follower count (standard view and up)Telegram
metricsobject | nullEngagement countsTelegram
metrics.likesinteger | nullLikesTelegram
metrics.commentsinteger | nullCommentsTelegram
metrics.sharesinteger | nullSharesTelegram
metrics.favoritesinteger | nullSavesTelegram
metrics.viewsinteger | nullViewsTelegram
metrics.repostsinteger | nullRepostsTelegram
imagesarray | nullImage addresses (standard view and up)Telegram
hashtagsarray | nullHashtags, without the # (standard view and up)Telegram
mentionsarray | nullAccounts mentioned in the text (standard view and up)Telegram
mentions[].idstring | nullAccount ID (standard view and up)Telegram
mentions[].usernamestring | nullHandle (standard view and up)Telegram
mentions[].namestring | nullDisplay name (standard view and up)Telegram
is_pinnedboolean | nullWhether the author pinned it (standard view and up)Telegram
post_idstring | nullID of the thread's root post when this is a reply; otherwise nullTelegram
parent_idstring | nullID of the item it replies to directly; otherwise nullTelegram
root_idstring | nullID of the first-level reply its thread hangs underTelegram
approximatearray | nullWhich numbers of this item are approximate or lower bounds; absent when all are exactTelegram
approximate[].fieldstring | nullPath of the field, such as metrics.viewsTelegram
approximate[].kindstring | nullApproximate, or a lower boundTelegram
extobjectThe platform's own fields (full view).Telegram
ext.numberinteger | nullThe message's number within its channel; with the channel's handle it locates the message (full view)Telegram
05

Unavailable fields

These published contract notes describe the capability boundary; fixtures do not establish live availability.

FieldReason
titleplatform
langcapability
author.idcapability
author.avatar_urlcapability
author.verifiedcapability
author.followerscapability
metrics.likesplatform
metrics.commentscapability
metrics.sharescapability
metrics.favoritesplatform
metrics.repostscapability
hashtagscapability
mentionscapability
is_pinnedcapability
post_idcapability
parent_idcapability
root_idcapability
06

Limits and checks

A successful request does not establish full coverage. Preserve the request ID, observation time, parameters and cursor, and inspect the returned items before analysis.

Local simulation uses TEST credits only. Real provider calls, real payments and external email are disabled. Historical reference-site prices are not DataNavoAPI prices.

  • Verify media URLs, counts and optional fields individually.
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗