DataNavoAPI / APIS / TELEGRAM

Telegram channel profile

Telegram channel profile: inspect inputs, account 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 channel profile uses /v1/telegram/channels/get; GET returns data.item with account objects.

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

  • Capability: telegram.channels.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.

  • Only send fields defined for this method; unknown fields are rejected before execution.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETusernamestringRequiredThe channel's handle, without the @—"telegram"
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.channels.get",
  "method": "GET",
  "params": {
    "username": "telegram"
  }
}
04

Output fields and interpretation

The account 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 | nullIDTelegram
usernamestring | nullHandleTelegram
namestring | nullDisplay nameTelegram
urlstring | nullLink to the profileTelegram
biostring | nullBioTelegram
avatar_urlstring | nullAvatar (standard view and up)Telegram
verifiedboolean | nullWhether the account is verified (standard view and up)Telegram
created_atstring | nullWhen the account was created (standard view and up)Telegram
metricsobject | nullAccount countsTelegram
metrics.followersinteger | nullFollowersTelegram
metrics.followinginteger | nullFollowingTelegram
metrics.postsinteger | nullPosts publishedTelegram
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
extobject—Telegram
05

Unavailable fields

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

FieldReason
idplatform
created_atcapability
metrics.followingplatform
metrics.postscapability
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 ↗