Telegram message detail
Telegram message detail: inspect inputs, post fields, pagination and limits, then run a local simulated request.
Copy the agent prompt manually
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.
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.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Optional / conditional | The channel's handle and the message's number joined by a slash, as in telegram/401 | — | "telegram/401" |
| GET | url | string | Optional / conditional | Link to the message: t.me, then the channel, then the number | — | — |
| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |
| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |
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.
{
"capability": "telegram.messages.get",
"method": "GET",
"params": {
"id": "telegram/401"
}
}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.
| Field | Type | Meaning | Source scope |
|---|---|---|---|
| id | string | null | ID; pass it unchanged to the get endpoint | Telegram |
| url | string | null | Link that opens the post | Telegram |
| type | string | null | Content format | Telegram |
| title | string | null | Title | Telegram |
| text | string | null | Body text | Telegram |
| lang | string | null | Language of the text (standard view and up) | Telegram |
| published_at | string | null | When it was published | Telegram |
| author | object | null | Author | Telegram |
| author.id | string | null | Author's account ID | Telegram |
| author.username | string | null | Author's handle | Telegram |
| author.name | string | null | Author's display name | Telegram |
| author.avatar_url | string | null | Author's avatar (standard view and up) | Telegram |
| author.verified | boolean | null | Whether the author is verified (standard view and up) | Telegram |
| author.followers | integer | null | Author's follower count (standard view and up) | Telegram |
| metrics | object | null | Engagement counts | Telegram |
| metrics.likes | integer | null | Likes | Telegram |
| metrics.comments | integer | null | Comments | Telegram |
| metrics.shares | integer | null | Shares | Telegram |
| metrics.favorites | integer | null | Saves | Telegram |
| metrics.views | integer | null | Views | Telegram |
| metrics.reposts | integer | null | Reposts | Telegram |
| images | array | null | Image addresses (standard view and up) | Telegram |
| hashtags | array | null | Hashtags, without the # (standard view and up) | Telegram |
| mentions | array | null | Accounts mentioned in the text (standard view and up) | Telegram |
| mentions[].id | string | null | Account ID (standard view and up) | Telegram |
| mentions[].username | string | null | Handle (standard view and up) | Telegram |
| mentions[].name | string | null | Display name (standard view and up) | Telegram |
| is_pinned | boolean | null | Whether the author pinned it (standard view and up) | Telegram |
| post_id | string | null | ID of the thread's root post when this is a reply; otherwise null | Telegram |
| parent_id | string | null | ID of the item it replies to directly; otherwise null | Telegram |
| root_id | string | null | ID of the first-level reply its thread hangs under | Telegram |
| approximate | array | null | Which numbers of this item are approximate or lower bounds; absent when all are exact | Telegram |
| approximate[].field | string | null | Path of the field, such as metrics.views | Telegram |
| approximate[].kind | string | null | Approximate, or a lower bound | Telegram |
| ext | object | The platform's own fields (full view). | Telegram |
| ext.number | integer | null | The message's number within its channel; with the channel's handle it locates the message (full view) | Telegram |
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.
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 ↗