Telegram Username Checker — Available or Taken

What does Telegram Username Checker do?

Telegram Username Checker tells you whether a Telegram @username is available or already taken. Users, channels, and bots share one public namespace. Paste a list of usernames (or t.me URLs), run the Actor, and download clean JSON / CSV / Excel from the dataset.

Built for bulk brand / handle research (up to 100,000 usernames per run). Large lists are auto-split into ~3,000-item child runs on Apify, with auto-heal under rate limits. Lightweight HTTP against public t.me pages - 256 MB, no browser.

This Actor is not affiliated with Telegram. Availability is inferred from public preview pages and can change if Telegram alters their HTML.

Key features

• Bulk checks - up to 100,000 usernames per run (invalid / duplicate inputs filtered before work starts)
• Shared namespace - users / channels / bots - one entityType: user mode
• Auto-sharding - runs above ~3,000 split into child runs; one parent dataset
• Auto-heal - on blocks / timeouts: backoff and lower concurrency
• URL-aware input - @user, user, or https://t.me/user
• No browser - fast HTTP (low compute)
• Success-only billing - only conclusive checks charge PPE result
• Export anywhere - JSON, CSV, Excel, HTML from the Apify dataset

Why Clovys

Clovys is a nonprofit organization driven by a single mission: to make the internet safer, faster, more reliable, and universally accessible.

We believe that data should not be locked behind exorbitant paywalls or complex technical barriers. By building lightweight, highly optimized Apify Actors, we help developers, researchers, and organizations access the information they need to innovate without friction.

As a nonprofit initiative, we do not optimize for margins. Our pricing is kept as low as possible and is strictly calculated to cover the raw infrastructure costs of data extraction - such as Apify compute units and proxy bandwidth.

For Telegram specifically, Clovys uses public t.me previews so bulk handle checks stay cheap and parallelizable.

Use cases

• Brand protection - see if your brand @ is free on Telegram
• Channel / bot naming - screen shortlists before launch
• Agency workflows - bulk-check client name ideas
• Multi-platform suites - pair with other Clovys username checkers

How to use

1. Open Telegram Username Checker in Apify Console
2. Paste usernames in Usernames
3. Keep defaults (256 MB, concurrency 3)
4. Click Start
5. Download results from the Dataset tab

Input

Field	Type	Default	Description
usernames	string[]	-	Usernames or t.me URLs (required, up to 100,000)
entityType	string	user	Always user (shared Telegram namespace)
maxConcurrency	integer	3	Parallel checks (1-10)
maxRetries	integer	2	Retries on network / ambiguous responses
requestDelayMs	integer	200	Pause after each check (0 = off)

Output example

You can download the dataset in JSON, HTML, CSV, or Excel.

{
 "platform": "telegram",
 "entityType": "user",
 "username": "telegram",
 "available": false,
 "displayName": "Telegram News",
 "profileUrl": "https://t.me/telegram",
 "method": "tme_public_page",
 "checkedAt": "2026-09-26T01:00:00.000Z",
 "error": null
}

Taken and available rows are successful results. Ambiguous / failed rows keep available: null and error set - they are not billed.

Data fields

Field	Description
platform	Always telegram
entityType	Always user
username	Normalized handle
available	true = free, false = taken, null = inconclusive
displayName	Public title when taken
profileUrl	https://t.me/{username}
method	Always tme_public_page
checkedAt	ISO timestamp
error	Error message if the check failed

Pricing

Pay-per-event pricing (platform usage is billed separately by Apify):

Event	When charged	Price
result	Each conclusive check (available true or false)	$0.004 ($4 / 1,000)
Actor Start	Once when the run starts (scaled by memory GB)	$0.001

Example: 1,000 conclusive checks ~ $4.00 in PPE result (+ Actor Start + Apify platform usage).

Only conclusive results are charged as result. Failed / ambiguous rows are free on the PPE event.

Recommended settings

Goal	Settings
Production / Store	256 MB, concurrency 3, delay 200 ms
High volume	concurrency 5-8, delay 50-100 ms
Huge lists	up to 100,000 usernames - auto-shard handles the rest

FAQ

How many usernames per run? Up to 100,000. Lists above ~3,000 are auto-split into child runs; invalid / duplicate inputs are dropped before sharding.

Is "taken" billed? Yes. Both available: false (taken) and available: true (free) are conclusive result events. Only error / inconclusive rows are free.

Are users, channels, and bots different namespaces? No. Telegram shares one public @username space - a taken channel blocks the same handle for a user.

Do I need expensive proxies? Usually no. If you hit rate limits at very high volume, lower concurrency or add Apify proxy.

What if a check fails? It is stored with error and available: null. Other usernames continue. Failed items are not billed as result.

Is this official Telegram data? No. This Actor is independent and unaffiliated.

Support

Questions, bugs, or feature requests: use the Actor Issues tab on Apify, or contact Clovys through the Store profile.