Telegram Profile

Affiliate disclosure: Some Apify links below include the aiagentapi referral parameter. TrueFetch may receive referral attribution when you use those links; your Actor price does not change.

Telegram Profile turns mixed Telegram identifiers into analysis-ready profiles for users, bots, channels, groups, and supergroups. Give it a bounded list of usernames, @handles, t.me links, accessible invites, or phone numbers and receive entity-specific fields plus a consistent status and provenance layer.

• The single required list accepts 1 to 1,000 targets, with the first 10 processed for free users.
• The published dataset defines 82 possible fields across five entity types rather than forcing unlike profiles into one narrow shape.
• The paired production path was live-tested on July 24, 2026 with one successful user row containing 53 fields and a stored photo.
• The Store page showed 1,004 total users, 94 monthly users, 99.7% successful runs, 17 bookmarks, and a 4.64/5 rating from 6 ratings on July 24, 2026.

Test one Telegram bot · Use Telegram Profile through the API

A FREE-tier run with one returned result has a $0.01300 fixed-event subtotal before variable actor_usage. Entity visibility, privacy, rate limits, profile changes, photos, runtime, and live pricing remain source-dependent. Submit only authorized identifiers, set a maximum total charge, and verify row statuses before acting on the data.

What does Telegram Profile do?

Telegram Profile resolves each supplied identifier and classifies the matching entity as a user, bot, channel, supergroup, or group. It then returns the fields applicable to that type. Every row retains the original input, processing time, status, processor link, numeric Telegram ID when available, known usernames, and an optional stored profile-photo URL.

People and bots can expose names, visible phone and language values, last-seen category, premium and verification state, scam, fake, deletion, support, and restriction flags. Bot rows may also contain commands, descriptions, menu links, active-user estimates, and capability settings. Communities can expose title, description, creation date, audience counts, join and forum settings, participant visibility, moderation counts, paid-feature flags, linked chats, and location.

This is a current profile lookup, not a conversation reader, participant census, identity certificate, contact-discovery promise, private-chat gateway, or historical-change tracker. Telegram decides which entity and attributes the Actor can see at run time.

How do I run Telegram Profile?

Open the Actor input page, submit one stable public target, and inspect the default dataset. The following bot handle is the shared scenario for every example on this page:

{
  "telegram_url": [
    "@BotFather"
  ]
}

Check status, type, id, and usernames first. Then review the fields relevant to the returned type. A completed run does not mean every input resolved, so compare the target list with dataset rows and keep the run ID.

Add other formats only after the one-target baseline works. A sensible second test mixes one @handle with one ordinary t.me username URL. Large unknown lists are harder to diagnose and may cost more through duplicate, not-found, or otherwise returned rows.

What data does Telegram Profile return?

The output is an 82-field union schema. A user or bot does not receive channel-only keys such as moderation counts, and a channel does not receive user-only call or last-seen fields. This type-aware design preserves useful detail while keeping the common fields stable.

Key field families include:

• Resolution and provenance: source_url, processor, processed_at, status, type, id, usernames, photo_url.
• User identity and visibility: names, phone, language, description, last seen, premium, verified, scam, fake, deleted, support, restriction, messaging and call settings.
• Bot capability: active users, commands, description, menu URL, main app, attachment menu, chat-history, editing, and business flags.
• Community profile: title, created date, member, online, administrator, kicked and banned counts, join settings, forum state, slow mode, participant visibility, bots, linked chats, and location.
• Business and extended detail: birthday, business hours, business location, greeting, away message, introduction, personal channel, star gifts, and paid-feature availability.

This abbreviated example contains supported bot fields; live values may differ:

{
  "source_url": "@BotFather",
  "processor": "https://apify.com/truefetch/telegram-profile?fpr=aiagentapi",
  "processed_at": "2026-07-24T07:00:00+00:00",
  "status": "success",
  "type": "bot",
  "id": 93372553,
  "usernames": [
    "BotFather"
  ],
  "first_name": "BotFather",
  "last_name": null,
  "phone": null,
  "is_verified": true,
  "is_scam": false,
  "is_fake": false,
  "profile_photo": true,
  "bot_has_main_app": true,
  "bot_commands": [
    "/newbot - create a new bot"
  ],
  "description": "Example visible profile text",
  "photo_url": "https://api.apify.com/v2/key-value-stores/STORE_ID/records/media-93372553.jpg"
}

Preserve null values: they distinguish unavailable or inapplicable data from a value you inferred elsewhere. Telegram flags and audience counts are observations, not independent verification.

What inputs can I configure?

telegram_url is required and must be an array with 1 to 1,000 entries. The name is retained for compatibility, but entries do not have to be full URLs. Supported strings include a username, @username, standard t.me username URL, accessible invite reference, or international phone number starting with +.

Free users are limited to the first 10 entries. An accessible invite means Telegram already permits the referenced chat to be resolved; submitting a link cannot grant membership. Phone resolution depends on source availability and visibility and must be used only with an appropriate legal basis.

The Actor does not remove duplicates. Repeated strings can create repeated output and repeated result events. Non-string entries may be ignored, so validate generated lists before a paid run. There is no country, language, entity-type, deduplication, or photo-disable input.

What platforms and markets does Telegram Profile cover?

Coverage is Telegram only. The target can represent a person, bot, broadcast channel, ordinary group, or supergroup. Both username-style identifiers and supported source links can be mixed in one request.

There is no geographic market selector. Any country or language coverage follows what the target exposes and what the platform returns. lang_code, phone, location, and business-location fields may be absent even when a profile is otherwise resolvable. The Actor does not translate text or enrich a Telegram record from an external source.

Why use Telegram Profile?

Use it when the decision starts with “what entity is this?” A mixed identifier list can be routed by type, filtered by status, reviewed for Telegram-supplied trust flags, or joined with an approved internal record by ID or username. The original source value and processing timestamp support reproducibility.

The broad union is especially useful when a workflow cannot know the entity type before lookup. It avoids separate initial calls for bots, people, and communities. At the same time, explicit nulls prevent the appearance that every field applies to every target.

Profile photos are stored separately and linked from dataset rows. That makes the tabular export compact while allowing authorized consumers to retrieve an available image. Dataset and file retention should be governed separately.

Who is Telegram Profile for?

Analysts can classify a known target list and review current community or bot attributes without manually opening each profile.

Operations teams can validate identifier formats and route supported entity types before a permitted downstream process.

Trust and safety teams can include scam, fake, verified, deleted, and restriction flags as source signals in a documented human review.

Developers and automation builders can obtain a consistent dataset through Apify API, schedules, webhooks, or MCP. The Actor is not suitable for covert monitoring, indiscriminate phone discovery, identity proof, or making consequential decisions from one flag.

How can I use Telegram Profile through the API or MCP?

The synchronous HTTP call below uses the same @BotFather input. Replace YOUR_TOKEN and store it as a secret:

curl -X POST "https://api.apify.com/v2/acts/awbkkk1w2CKtNBScC/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"telegram_url":["@BotFather"]}'

Configure an MCP client according to the Apify MCP guide:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?token=YOUR_TOKEN"
    }
  }
}

Then request the Actor with the same scenario:

{
  "actor": "truefetch/telegram-profile",
  "input": {
    "telegram_url": [
      "@BotFather"
    ]
  }
}

For a longer list, start asynchronously, poll until terminal state, fetch the default dataset, and inspect both row count and statuses. Apply a maximum total charge and bound automatic retries. MCP availability can depend on the plan and credentials used by the calling client.

How much does Telegram Profile cost?

The current configuration combines one start event, variable usage events, and one result event for each normally returned dataset row. A normal not found row can carry the result event; a temporarily unavailable row can follow an uncharged result path.

Billed event	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Actor start	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000
Actor usage	$0.00001/event	$0.00001/event	$0.00001/event	$0.00001/event	$0.00001/event	$0.00001/event
Result row	$0.00300	$0.00290	$0.00280	$0.00270	$0.00270	$0.00270

The smallest useful FREE-tier calculation is $0.01000 + 1 × $0.00300 = $0.01300, before variable actor_usage. Duplicate targets and not-found rows can affect total result events. Check the live pricing page before budgeting because published prices and platform charges can change.

How does Telegram Profile compare with alternatives?

Manual lookup is convenient for one target but does not provide a repeatable dataset, original-input mapping, processing timestamp, or batch status review. A general browser extractor may capture visible page text but lacks this entity-specific union and stable Telegram field names.

Telegram Channel Message is better when the unit of work is a message. Telegram Group Member is designed for visible participant data. Telegram Profile should be the first step when the goal is entity classification and current profile metadata.

For continuous change tracking, schedule bounded runs and store snapshots in your own approved system; this Actor returns current observations and does not calculate historical differences.

What are the limits and troubleshooting steps?

Each target requires separate source work and deliberate pacing, so a 1,000-entry list can take substantial time. Start with one target, then 10, and measure the result before increasing volume. Photos add storage and transfer work.

If status is not found, retry the canonical username without unrelated query parameters. Invite links work only when already accessible. Phone targets must begin with +, and resolution is not guaranteed. temporarily unavailable, try again later indicates a transient or unclassified source problem rather than proof that the entity does not exist.

If terminal status is successful but rows are missing, treat the run as incomplete. Compare input and output counts, review status values, inspect the key-value store separately, retain the run ID, and contact support before resubmitting a paid list. Photos and dataset rows are separate resources and may not remain one-to-one after a partial failure.

Frequently asked questions

Will every row contain 82 fields?

No. Eighty-two is the complete union. Each entity type returns its applicable subset.

Can I combine bots, people, channels, and groups?

Yes. Mixed string targets are supported in one input array.

Does an invite link let the Actor join a private group?

No. It resolves only when the referenced chat is already accessible; the link does not grant access.

Is a Telegram flag proof that an account is safe or unsafe?

No. Treat verified, scam, fake, restricted, and related fields as platform observations for review, not conclusive evidence.

Why did a free run ignore targets after the tenth?

The current runtime limits free users to the first 10 entries even though the schema accepts up to 1,000.

Related TrueFetch Actors

• Telegram Group Member returns visible community participant profiles where access permits.
• Telegram Channel Message exports public username-addressable message history with optional media.
• X User Profile adds a separate public-profile surface for authorized cross-platform research.

Support and last updated

Contact the TrueFetch group or support with the Actor name, run ID, sanitized target formats, expected rows, actual rows, and observed statuses. Never post tokens, private phone numbers, downloaded personal files, or other secrets.

Process only data you are authorized to use. Follow Telegram terms, applicable law, privacy requirements, copyright, and retention policies. Do not use the Actor for harassment, surveillance, spam, doxxing, sensitive profiling, unauthorized contact discovery, or redistribution.

Last updated: July 24, 2026.